You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9981085
Browse filesBrowse the repository at this point in the historyBrowse files
To use only one coding agent, run `just login-codex` or `just login-claude`,
68
+
followed by `just login-datadog login-fastly`.
69
+
62
70
### 3. Set up projects
63
71
64
72
The host directory `~/buddy` is mounted inside the VM at `$HOME/work`.
@@ -86,7 +94,12 @@ Place your projects in the host directory:
86
94
ssh lima-buddy
87
95
```
88
96
89
-
- (Optional) Launch the `codex`command inside the VM to start the Codex TUI.
97
+
- Launch `codex` or `claude` inside the VM from your project directory:
98
+
99
+
```sh
100
+
cd ~/work/<project>
101
+
claude
102
+
```
90
103
91
104
See the [Lima SSH documentation](https://lima-vm.io/docs/usage/ssh/) for more details.
92
105
@@ -112,6 +125,10 @@ for more details.
112
125
113
126
- Check the [justfile](./justfile) for other available commands.
114
127
128
+
- Run `just upgrade` to update the guest and both coding agents. This also
129
+
installs Claude Code in an existing VM. New VMs install it automatically
130
+
using the [native installer](https://code.claude.com/docs/en/installation).
131
+
115
132
- Run commands in the VM:
116
133
117
134
```sh
@@ -134,14 +151,14 @@ for more details.
134
151
135
152
The template explicitly sets `user.passwordlessSudo: true`, which is
136
153
[Lima's default for Linux guests](https://lima-vm.io/docs/config/sudo/).
137
-
This gives Codex unrestricted root access inside the guest, but does not grant
138
-
root access on the host. The VM boundary and the resources exposed to the VM,
139
-
such as the writable `$HOME/work` mount, remain the main security boundary.
154
+
This gives Codex and Claude Code unrestricted root access inside the guest, but
155
+
does not grant root access on the host. The VM boundary and the resources exposed
156
+
to the VM, such as the writable `$HOME/work` mount, remain the main security boundary.
140
157
141
158
Enabling passwordless sudo has this advantage:
142
159
143
-
- Codexand other automation can install packages, update the guest, and fix
144
-
system configuration without waiting for a password prompt.
160
+
- Codex, Claude Code, and other automation can install packages, update the guest,
161
+
and fix system configuration without waiting for a password prompt.
145
162
146
163
It also has these disadvantages:
147
164
@@ -154,10 +171,10 @@ It also has these disadvantages:
154
171
155
172
## FAQ
156
173
157
-
> Why not running Codex directly on the host?
174
+
> Why not run Codex or Claude Code directly on the host?
158
175
159
-
Auditing all commands that codex wants to run is not productive. Instead, by
160
-
running it in an isolated VM, you can run codex in yolo mode.
176
+
Auditing all commands that coding agents want to run is not productive. Running
177
+
them in an isolated VM lets you give them full permissions inside the guest.
161
178
162
179
> Why not using one VM per project?
163
180
@@ -174,10 +191,10 @@ Lima provides:
174
191
- It's an open source [CNCF project](https://www.cncf.io/projects/lima/), while Docker Desktop is a proprietary product.
175
192
- The Docker Desktop feature [Enhanced Container Isolation](https://docs.docker.com/enterprise/security/hardened-desktop/enhanced-container-isolation/), which "prevents malicious containers from compromising the host system" is restricted to Docker Business.
176
193
177
-
> I don't want to run codex with full privileges, I think it is dangerous!
194
+
> I don't want to run coding agents with full privileges, I think it is dangerous!
178
195
179
-
Nobody forces you to run codex with full privileges. You can still run it in the
180
-
`buddy` VM for improved security _and_ customize its permissions.
196
+
Nobody forces you to run Codex or Claude Code with full privileges. You can still
197
+
run either in the `buddy` VM for improved security _and_ customize its permissions.
0 commit comments