Skip to content

Commit a415cd4

Browse files
ThomasK33claude
andcommitted
feat: add @coder/ai-sdk-eve-sandbox (Coder backend for Vercel eve)
New package implementing Vercel eve's `SandboxBackend` contract so eve agents run their sandbox (bash/read/write/glob/grep) inside a Coder workspace. - Reuses @coder/ai-sdk-sandbox (createCoderWorkspace + transport + session) for workspace get-or-create, wait-for-ready, and $HOME resolution; only resolvePath/removePath/setNetworkPolicy are added on top. - `eve` is a type-only peer dependency, so the repo's pinned ai/@ai-sdk version chain is untouched (pnpm added eve to minimumReleaseAgeExclude). - Coder-specific behavior: prewarm is a no-op (Coder templates are server-side, no build-time capture), setNetworkPolicy throws on non-allow-all unless opted out, and dispose defaults to "keep" (leave the workspace running for fast reattach). - dispose "stop"/"delete" only act on workspaces this backend provisions per session; an explicitly-named (borrowed) workspace is never torn down. - removePath refuses empty / working-dir / root targets to avoid a stray rm -rf. - 17 mock-transport tests; typecheck, build, oxlint, oxfmt, publint, and attw all pass. Wired into release-please, the PR-title scope check, and root publint/attw scripts. Change-Id: Iabac131f8babda3ee5d22959206326b3acbf8b4d Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Thomas Kosiewski <tk@coder.com>
1 parent 92aed19 commit a415cd4

15 files changed

Lines changed: 1686 additions & 4 deletions

.github/workflows/pr-title.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,7 @@ jobs:
4040
chore
4141
scopes: |
4242
sandbox
43+
eve-sandbox
4344
agent
4445
provider
4546
requireScope: false

.release-please-manifest.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
{
22
"packages/sandbox": "0.1.0",
33
"packages/agent": "0.1.0",
4-
"packages/provider": "0.1.0"
4+
"packages/provider": "0.1.0",
5+
"packages/eve-sandbox": "0.1.0"
56
}

package.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"name": "coder-ai-sdk",
33
"version": "0.0.0",
44
"private": true,
5-
"description": "Monorepo for Coder's Vercel AI SDK packages (@coder/ai-sdk-sandbox, @coder/ai-sdk-agent, @coder/ai-sdk-provider).",
5+
"description": "Monorepo for Coder's Vercel AI SDK packages (@coder/ai-sdk-sandbox, @coder/ai-sdk-eve-sandbox, @coder/ai-sdk-agent, @coder/ai-sdk-provider).",
66
"homepage": "https://github.com/coder/ai-sdk#readme",
77
"bugs": {
88
"url": "https://github.com/coder/ai-sdk/issues"
@@ -24,8 +24,8 @@
2424
"format": "oxfmt .",
2525
"format:check": "oxfmt --check .",
2626
"check": "oxfmt --check . && oxlint && pnpm -r typecheck",
27-
"publint": "pnpm --filter @coder/ai-sdk-sandbox --filter @coder/ai-sdk-provider exec publint",
28-
"attw": "pnpm --filter @coder/ai-sdk-sandbox --filter @coder/ai-sdk-provider attw"
27+
"publint": "pnpm --filter @coder/ai-sdk-sandbox --filter @coder/ai-sdk-eve-sandbox --filter @coder/ai-sdk-provider exec publint",
28+
"attw": "pnpm --filter @coder/ai-sdk-sandbox --filter @coder/ai-sdk-eve-sandbox --filter @coder/ai-sdk-provider attw"
2929
},
3030
"devDependencies": {
3131
"oxfmt": "^0.55.0",

packages/eve-sandbox/LICENSE

Lines changed: 202 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,202 @@
1+
2+
Apache License
3+
Version 2.0, January 2004
4+
http://www.apache.org/licenses/
5+
6+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7+
8+
1. Definitions.
9+
10+
"License" shall mean the terms and conditions for use, reproduction,
11+
and distribution as defined by Sections 1 through 9 of this document.
12+
13+
"Licensor" shall mean the copyright owner or entity authorized by
14+
the copyright owner that is granting the License.
15+
16+
"Legal Entity" shall mean the union of the acting entity and all
17+
other entities that control, are controlled by, or are under common
18+
control with that entity. For the purposes of this definition,
19+
"control" means (i) the power, direct or indirect, to cause the
20+
direction or management of such entity, whether by contract or
21+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
22+
outstanding shares, or (iii) beneficial ownership of such entity.
23+
24+
"You" (or "Your") shall mean an individual or Legal Entity
25+
exercising permissions granted by this License.
26+
27+
"Source" form shall mean the preferred form for making modifications,
28+
including but not limited to software source code, documentation
29+
source, and configuration files.
30+
31+
"Object" form shall mean any form resulting from mechanical
32+
transformation or translation of a Source form, including but
33+
not limited to compiled object code, generated documentation,
34+
and conversions to other media types.
35+
36+
"Work" shall mean the work of authorship, whether in Source or
37+
Object form, made available under the License, as indicated by a
38+
copyright notice that is included in or attached to the work
39+
(an example is provided in the Appendix below).
40+
41+
"Derivative Works" shall mean any work, whether in Source or Object
42+
form, that is based on (or derived from) the Work and for which the
43+
editorial revisions, annotations, elaborations, or other modifications
44+
represent, as a whole, an original work of authorship. For the purposes
45+
of this License, Derivative Works shall not include works that remain
46+
separable from, or merely link (or bind by name) to the interfaces of,
47+
the Work and Derivative Works thereof.
48+
49+
"Contribution" shall mean any work of authorship, including
50+
the original version of the Work and any modifications or additions
51+
to that Work or Derivative Works thereof, that is intentionally
52+
submitted to Licensor for inclusion in the Work by the copyright owner
53+
or by an individual or Legal Entity authorized to submit on behalf of
54+
the copyright owner. For the purposes of this definition, "submitted"
55+
means any form of electronic, verbal, or written communication sent
56+
to the Licensor or its representatives, including but not limited to
57+
communication on electronic mailing lists, source code control systems,
58+
and issue tracking systems that are managed by, or on behalf of, the
59+
Licensor for the purpose of discussing and improving the Work, but
60+
excluding communication that is conspicuously marked or otherwise
61+
designated in writing by the copyright owner as "Not a Contribution."
62+
63+
"Contributor" shall mean Licensor and any individual or Legal Entity
64+
on behalf of whom a Contribution has been received by Licensor and
65+
subsequently incorporated within the Work.
66+
67+
2. Grant of Copyright License. Subject to the terms and conditions of
68+
this License, each Contributor hereby grants to You a perpetual,
69+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70+
copyright license to reproduce, prepare Derivative Works of,
71+
publicly display, publicly perform, sublicense, and distribute the
72+
Work and such Derivative Works in Source or Object form.
73+
74+
3. Grant of Patent License. Subject to the terms and conditions of
75+
this License, each Contributor hereby grants to You a perpetual,
76+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77+
(except as stated in this section) patent license to make, have made,
78+
use, offer to sell, sell, import, and otherwise transfer the Work,
79+
where such license applies only to those patent claims licensable
80+
by such Contributor that are necessarily infringed by their
81+
Contribution(s) alone or by combination of their Contribution(s)
82+
with the Work to which such Contribution(s) was submitted. If You
83+
institute patent litigation against any entity (including a
84+
cross-claim or counterclaim in a lawsuit) alleging that the Work
85+
or a Contribution incorporated within the Work constitutes direct
86+
or contributory patent infringement, then any patent licenses
87+
granted to You under this License for that Work shall terminate
88+
as of the date such litigation is filed.
89+
90+
4. Redistribution. You may reproduce and distribute copies of the
91+
Work or Derivative Works thereof in any medium, with or without
92+
modifications, and in Source or Object form, provided that You
93+
meet the following conditions:
94+
95+
(a) You must give any other recipients of the Work or
96+
Derivative Works a copy of this License; and
97+
98+
(b) You must cause any modified files to carry prominent notices
99+
stating that You changed the files; and
100+
101+
(c) You must retain, in the Source form of any Derivative Works
102+
that You distribute, all copyright, patent, trademark, and
103+
attribution notices from the Source form of the Work,
104+
excluding those notices that do not pertain to any part of
105+
the Derivative Works; and
106+
107+
(d) If the Work includes a "NOTICE" text file as part of its
108+
distribution, then any Derivative Works that You distribute must
109+
include a readable copy of the attribution notices contained
110+
within such NOTICE file, excluding those notices that do not
111+
pertain to any part of the Derivative Works, in at least one
112+
of the following places: within a NOTICE text file distributed
113+
as part of the Derivative Works; within the Source form or
114+
documentation, if provided along with the Derivative Works; or,
115+
within a display generated by the Derivative Works, if and
116+
wherever such third-party notices normally appear. The contents
117+
of the NOTICE file are for informational purposes only and
118+
do not modify the License. You may add Your own attribution
119+
notices within Derivative Works that You distribute, alongside
120+
or as an addendum to the NOTICE text from the Work, provided
121+
that such additional attribution notices cannot be construed
122+
as modifying the License.
123+
124+
You may add Your own copyright statement to Your modifications and
125+
may provide additional or different license terms and conditions
126+
for use, reproduction, or distribution of Your modifications, or
127+
for any such Derivative Works as a whole, provided Your use,
128+
reproduction, and distribution of the Work otherwise complies with
129+
the conditions stated in this License.
130+
131+
5. Submission of Contributions. Unless You explicitly state otherwise,
132+
any Contribution intentionally submitted for inclusion in the Work
133+
by You to the Licensor shall be under the terms and conditions of
134+
this License, without any additional terms or conditions.
135+
Notwithstanding the above, nothing herein shall supersede or modify
136+
the terms of any separate license agreement you may have executed
137+
with Licensor regarding such Contributions.
138+
139+
6. Trademarks. This License does not grant permission to use the trade
140+
names, trademarks, service marks, or product names of the Licensor,
141+
except as required for reasonable and customary use in describing the
142+
origin of the Work and reproducing the content of the NOTICE file.
143+
144+
7. Disclaimer of Warranty. Unless required by applicable law or
145+
agreed to in writing, Licensor provides the Work (and each
146+
Contributor provides its Contributions) on an "AS IS" BASIS,
147+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148+
implied, including, without limitation, any warranties or conditions
149+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150+
PARTICULAR PURPOSE. You are solely responsible for determining the
151+
appropriateness of using or redistributing the Work and assume any
152+
risks associated with Your exercise of permissions under this License.
153+
154+
8. Limitation of Liability. In no event and under no legal theory,
155+
whether in tort (including negligence), contract, or otherwise,
156+
unless required by applicable law (such as deliberate and grossly
157+
negligent acts) or agreed to in writing, shall any Contributor be
158+
liable to You for damages, including any direct, indirect, special,
159+
incidental, or consequential damages of any character arising as a
160+
result of this License or out of the use or inability to use the
161+
Work (including but not limited to damages for loss of goodwill,
162+
work stoppage, computer failure or malfunction, or any and all
163+
other commercial damages or losses), even if such Contributor
164+
has been advised of the possibility of such damages.
165+
166+
9. Accepting Warranty or Additional Liability. While redistributing
167+
the Work or Derivative Works thereof, You may choose to offer,
168+
and charge a fee for, acceptance of support, warranty, indemnity,
169+
or other liability obligations and/or rights consistent with this
170+
License. However, in accepting such obligations, You may act only
171+
on Your own behalf and on Your sole responsibility, not on behalf
172+
of any other Contributor, and only if You agree to indemnify,
173+
defend, and hold each Contributor harmless for any liability
174+
incurred by, or claims asserted against, such Contributor by reason
175+
of your accepting any such warranty or additional liability.
176+
177+
END OF TERMS AND CONDITIONS
178+
179+
APPENDIX: How to apply the Apache License to your work.
180+
181+
To apply the Apache License to your work, attach the following
182+
boilerplate notice, with the fields enclosed by brackets "[]"
183+
replaced with your own identifying information. (Don't include
184+
the brackets!) The text should be enclosed in the appropriate
185+
comment syntax for the file format. We also recommend that a
186+
file or class name and description of purpose be included on the
187+
same "printed page" as the copyright notice for easier
188+
identification within third-party archives.
189+
190+
Copyright [yyyy] [name of copyright owner]
191+
192+
Licensed under the Apache License, Version 2.0 (the "License");
193+
you may not use this file except in compliance with the License.
194+
You may obtain a copy of the License at
195+
196+
http://www.apache.org/licenses/LICENSE-2.0
197+
198+
Unless required by applicable law or agreed to in writing, software
199+
distributed under the License is distributed on an "AS IS" BASIS,
200+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201+
See the License for the specific language governing permissions and
202+
limitations under the License.

packages/eve-sandbox/README.md

Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
# @coder/ai-sdk-eve-sandbox
2+
3+
A [Coder](https://coder.com) workspace sandbox **backend** for Vercel's [eve](https://github.com/vercel/eve) agent framework. It lets an eve agent run its sandbox (the `bash`, `read_file`, `write_file`, `glob`, `grep` tools) inside a real, long-lived Coder workspace instead of an ephemeral cloud microVM.
4+
5+
It implements eve's public `SandboxBackend` contract, so you pass it to `defineSandbox` exactly like the built-in `docker()` / `vercel()` backends:
6+
7+
```ts
8+
// agent/sandbox.ts
9+
import { defineSandbox } from "eve/sandbox";
10+
import { createCoderSandboxBackend } from "@coder/ai-sdk-eve-sandbox";
11+
12+
export default defineSandbox({
13+
// One Coder workspace per eve session, provisioned from a template:
14+
backend: createCoderSandboxBackend({
15+
create: { template: "docker", preset: "Large" },
16+
}),
17+
});
18+
```
19+
20+
Or attach to a single, pre-existing workspace:
21+
22+
```ts
23+
defineSandbox({
24+
backend: createCoderSandboxBackend({ workspace: "my-dev-workspace" }),
25+
});
26+
```
27+
28+
> **Status:** experimental, and tracks a fast-moving target. eve is in public beta (`eve@0.11.5` at time of writing) and its sandbox interfaces may change before GA. Pin versions and expect churn.
29+
30+
## Install
31+
32+
```bash
33+
pnpm add @coder/ai-sdk-eve-sandbox eve
34+
```
35+
36+
`eve` is a peer dependency (your app provides it). The package reaches Coder through the [`coder` CLI](https://coder.com/docs/install) over SSH by default, so an authenticated `coder login` (or an explicit `url`/`token`) must be available wherever the agent runs.
37+
38+
> Because this package builds on `@coder/ai-sdk-sandbox`, your package manager may report `@ai-sdk/harness` and `@ai-sdk/provider-utils` as unmet peers. They are **type-only** there and are not needed at runtime; install them only if you typecheck against this package's internals.
39+
40+
## How it maps onto Coder
41+
42+
eve's sandbox abstraction and `@coder/ai-sdk-sandbox` both build their I/O surface on the Vercel AI SDK's `Experimental_SandboxSession`, so the file/exec layer maps over directly. This backend reuses `@coder/ai-sdk-sandbox` for workspace orchestration (get-or-create, wait-for-ready, `$HOME` resolution, preset validation) and adapts the result to eve's `SandboxSession`.
43+
44+
| eve `SandboxBackend` | Coder mapping |
45+
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
46+
| `create({ sessionKey, existingMetadata })` | Get-or-create a workspace (per-session name derived from `sessionKey`, or your fixed `workspace`); `existingMetadata` ⇒ reattach. Waits for the agent to be ready. |
47+
| `SandboxSession.run` / `spawn` | `coder ssh` exec / streamed process |
48+
| `SandboxSession.read*/write*File` | base64 over `coder ssh` |
49+
| `SandboxSession.removePath` | `rm` over `coder ssh` |
50+
| `SandboxSession.resolvePath` | anchors relative paths at the workspace working directory (see caveats) |
51+
| `handle.captureState()` | `{ backendName: "coder", metadata: { workspace }, sessionKey }` |
52+
| `handle.dispose()` | per `dispose` policy — keep / stop / delete (default **keep**) |
53+
54+
## Settings
55+
56+
`createCoderSandboxBackend(settings)`:
57+
58+
- `workspace?` — attach to an existing `[owner/]workspace[.agent]` (fixed string or a resolver from the session key). With `create`, it is get-or-created.
59+
- `create?` — provision from a Coder template (`template`, `preset`, `parameters`, …). Without an explicit `workspace`, eve gets **one workspace per session**.
60+
- `transport?` — defaults to a `CoderCliTransport` over an ambient `coder login`. Use `new CoderCliTransport({ url, token })` (re-exported from this package) for explicit auth.
61+
- `defaultWorkingDirectory?` — defaults to the workspace `$HOME`.
62+
- `readyTimeoutMs?` — agent-readiness timeout (default `300000`).
63+
- `dispose?``"keep"` (default), `"stop"`, or `"delete"`. `"stop"`/`"delete"` apply only to per-session workspaces this backend provisions (create mode without an explicit `workspace`); an explicitly named workspace is treated as borrowed and never stopped/deleted. **At least one of `workspace` or `create` is required.**
64+
- `allowUnsafeNetworkPolicy?` — see below.
65+
66+
## Caveats specific to Coder
67+
68+
These follow from eve's model meeting Coder's, not from missing work:
69+
70+
- **`prewarm` is a near no-op.** Coder templates are provisioned server-side (Terraform), so there is no build-time template snapshot to capture, and eve `seedFiles` are **not** baked in. Bake setup into your Coder template, or write files from a sandbox `onSession` hook.
71+
- **`setNetworkPolicy` is not enforceable.** Egress is governed by your Coder template/deployment, not this backend. Anything other than `"allow-all"` **throws** by default (rather than implying containment that isn't there). Pass `allowUnsafeNetworkPolicy: true` to treat it as a no-op — but note that eve features relying on firewall **credential brokering** (e.g. the GitHub channel injecting auth headers via `setNetworkPolicy`) then silently do _not_ broker, so those flows are unsupported here.
72+
- **Per-session workspaces have provisioning latency.** A fresh workspace is a Terraform build (minutes); set `readyTimeoutMs` accordingly. Reattach to an already-running workspace is fast — which is why `dispose` defaults to **keep**.
73+
- **Relative paths anchor at the workspace working directory** (`$HOME` by default), not eve's `/workspace` root. eve features that write to _absolute_ `/workspace` paths (e.g. skill injection, attachment staging) require that path to exist and be writable in your Coder workspace image.
74+
75+
## License
76+
77+
Apache-2.0

0 commit comments

Comments
 (0)