coder/ai-sdk

Coder's integrations with the Vercel AI SDK. Run coding agents inside Coder workspaces, and drive Coder Agents from AI SDK code.

Note

All three packages are pre-1.0 and track experimental upstreams (Coder's chat API is experimental). Expect breaking changes.

Packages

Each package is published to npm independently and ships its own README with full install instructions, usage, and API docs.

Package	Version	What it does
`@coder/ai-sdk-sandbox`		A sandbox provider for the Vercel AI SDK v7 `HarnessAgent`. Runs CLI coding agents — Claude Code, Codex — inside a Coder workspace instead of on the local machine, so each agent gets a real, isolated dev environment with your tools, secrets, and network.
`@coder/ai-sdk-agent`		A Vercel AI SDK–compliant `Agent` (AI SDK v7) backed by Coder Agents, Coder's server-side agent runtime. `new CoderAgent()` returns a real `Agent` — `generate()`, `stream()`, tool calls, the whole interface.
`@coder/ai-sdk-provider`		A Vercel AI SDK provider that routes `generateText` / `streamText` calls through your Coder deployment's AI Gateway. Point it at your deployment with a Coder API token and use any model it proxies — no raw provider keys, with per-user auth and audit.

Experimental: @coder/ai-sdk-effect bridges these packages to Effect (unpublished Phase 1 spike, see #144).

Which package? Need a model (text, streaming, or schema‑constrained structured output) through your deployment → @coder/ai-sdk-provider. Need Coder's server‑side agent (multi‑step tool loop, MCP, workspace file/shell tools) → @coder/ai-sdk-agent. Need to run a CLI coding agent (Claude Code, Codex) inside a workspace → @coder/ai-sdk-sandbox.

Using them together

The packages are independent, but they compose into one application against one deployment, authenticated by one Coder token: provision a workspace with the sandbox package, drive Coder's server-side agent in it with the agent package, then extract a typed result with the provider. The full flow below audits a project's dependencies — the agent works inside the workspace (calling one custom tool that executes in your process), and the provider parses the prose report into a typed object through AI Gateway.

pnpm add @coder/ai-sdk-sandbox @coder/ai-sdk-agent @coder/ai-sdk-provider ai zod
pnpm add @ai-sdk/harness @ai-sdk/provider-utils # peer dependencies of the sandbox packageexport CODER_URL=https://coder.example.com
export CODER_SESSION_TOKEN=$(coder tokens create --name compose-example)export CODER_ORG_ID=<org-uuid># e.g. the first `organization_ids` entry from /api/v2/users/me

import{generateObject,tool}from"ai";import{z}from"zod";import{CoderNativeTransport,ensureCoderWorkspace}from"@coder/ai-sdk-sandbox";import{CoderAgent}from"@coder/ai-sdk-agent";import{createCoder}from"@coder/ai-sdk-provider";// The sandbox transport and the agent both default their connection from the// CODER_URL + CODER_SESSION_TOKEN exported above (explicit `url`/`baseUrl` and// `token` options remain available).// 1. Sandbox: get-or-create a workspace and wait until its agent is ready.// The native transport talks straight to your deployment — no `coder` CLI// or `ssh` on the host. Assumes the template checks out your project.consttransport=newCoderNativeTransport();constws=awaitensureCoderWorkspace({workspace: "dep-audit",create: {template: "docker"},
transport,});if(ws.id===undefined)thrownewError("transport did not report a workspace id");// 2. Agent: drive Coder's server-side agent loop in that workspace. The// server runs the multi-step loop and its file/shell tools; your custom// tool executes here, in this process, and its result is sent back.constagent=newCoderAgent({organizationId: process.env.CODER_ORG_ID!,model: "claude-sonnet-4-6",workspaceId: ws.id,// binds the chat's workspace-scoped toolsinstructions: "Audit the project in the workspace. Use latestVersion to check dependencies.",tools: {latestVersion: tool({description: "Look up the latest published version of an npm package.",inputSchema: z.object({pkg: z.string()}),execute: async({ pkg })=>{constres=awaitfetch(`https://registry.npmjs.org/${encodeURIComponent(pkg)}/latest`);if(!res.ok)return{ pkg,error: `registry returned ${res.status}`};const{ version }=(awaitres.json())as{version: string};return{ pkg, version };},}),},});letreport: string;try{constresult=awaitagent.generate({prompt:
"Read package.json, compare the dependencies against their latest versions, and report on the project's dependency health.",});report=result.text;}finally{awaitagent.archive();// archives the chat; never deletes the workspace}// 3. Provider: schema-constrained extraction through AI Gateway. The provider// takes explicit credentials (its `apiKey` is dual-purpose in BYOK mode).constcoder=createCoder({baseURL: process.env.CODER_URL!,apiKey: process.env.CODER_SESSION_TOKEN!,});const{object: audit}=awaitgenerateObject({model: coder("claude-sonnet-4-6"),schema: z.object({health: z.enum(["good","aging","at-risk"]),outdated: z.array(z.object({pkg: z.string(),current: z.string(),latest: z.string()})),summary: z.string(),}),prompt: `Extract the dependency audit from this report:\n\n${report}`,});console.log(audit.health,audit.summary);console.table(audit.outdated);awaittransport.close();// close cached relay WebSockets on shutdown

Each step stands alone — skip the ones you don't need. For depth on each: ensureCoderWorkspace and workspace creation settings in the sandbox README; custom tools, structured output (when the typed answer must come out of the agent run itself, not a follow-up model call), the workspaces & quota operations guide (fleet sizing, autostop, troubleshooting stuck turns), and the durable-workflow how-to (persisting chatId across job/queue boundaries, drop & timeout recovery) in the agent README; named providers and authentication modes and the enterprise governance & security reference (data flow, credential isolation, audit capture, required permissions) in the provider README.

Contributing

Development setup, the command reference, and how releases work all live in CONTRIBUTING.md. The short version — with mise installed:

mise install && pnpm install # set up the toolchain + dependencies
pnpm check && pnpm test# format check, lint, typecheck, then test

License

Apache-2.0 © Coder Technologies, Inc.

coder/ai-sdk

Coder's integrations with the Vercel AI SDK. Run coding agents inside Coder workspaces, and drive Coder Agents from AI SDK code.

Note

All three packages are pre-1.0 and track experimental upstreams (Coder's chat API is experimental). Expect breaking changes.

Packages

Each package is published to npm independently and ships its own README with full install instructions, usage, and API docs.

Package	Version	What it does
`@coder/ai-sdk-sandbox`		A sandbox provider for the Vercel AI SDK v7 `HarnessAgent`. Runs CLI coding agents — Claude Code, Codex — inside a Coder workspace instead of on the local machine, so each agent gets a real, isolated dev environment with your tools, secrets, and network.
`@coder/ai-sdk-agent`		A Vercel AI SDK–compliant `Agent` (AI SDK v7) backed by Coder Agents, Coder's server-side agent runtime. `new CoderAgent()` returns a real `Agent` — `generate()`, `stream()`, tool calls, the whole interface.
`@coder/ai-sdk-provider`		A Vercel AI SDK provider that routes `generateText` / `streamText` calls through your Coder deployment's AI Gateway. Point it at your deployment with a Coder API token and use any model it proxies — no raw provider keys, with per-user auth and audit.

Experimental: @coder/ai-sdk-effect bridges these packages to Effect (unpublished Phase 1 spike, see #144).

Which package? Need a model (text, streaming, or schema‑constrained structured output) through your deployment → @coder/ai-sdk-provider. Need Coder's server‑side agent (multi‑step tool loop, MCP, workspace file/shell tools) → @coder/ai-sdk-agent. Need to run a CLI coding agent (Claude Code, Codex) inside a workspace → @coder/ai-sdk-sandbox.

Using them together

The packages are independent, but they compose into one application against one deployment, authenticated by one Coder token: provision a workspace with the sandbox package, drive Coder's server-side agent in it with the agent package, then extract a typed result with the provider. The full flow below audits a project's dependencies — the agent works inside the workspace (calling one custom tool that executes in your process), and the provider parses the prose report into a typed object through AI Gateway.

pnpm add @coder/ai-sdk-sandbox @coder/ai-sdk-agent @coder/ai-sdk-provider ai zod
pnpm add @ai-sdk/harness @ai-sdk/provider-utils # peer dependencies of the sandbox packageexport CODER_URL=https://coder.example.com
export CODER_SESSION_TOKEN=$(coder tokens create --name compose-example)export CODER_ORG_ID=<org-uuid># e.g. the first `organization_ids` entry from /api/v2/users/me

import{generateObject,tool}from"ai";import{z}from"zod";import{CoderNativeTransport,ensureCoderWorkspace}from"@coder/ai-sdk-sandbox";import{CoderAgent}from"@coder/ai-sdk-agent";import{createCoder}from"@coder/ai-sdk-provider";// The sandbox transport and the agent both default their connection from the// CODER_URL + CODER_SESSION_TOKEN exported above (explicit `url`/`baseUrl` and// `token` options remain available).// 1. Sandbox: get-or-create a workspace and wait until its agent is ready.// The native transport talks straight to your deployment — no `coder` CLI// or `ssh` on the host. Assumes the template checks out your project.consttransport=newCoderNativeTransport();constws=awaitensureCoderWorkspace({workspace: "dep-audit",create: {template: "docker"},
transport,});if(ws.id===undefined)thrownewError("transport did not report a workspace id");// 2. Agent: drive Coder's server-side agent loop in that workspace. The// server runs the multi-step loop and its file/shell tools; your custom// tool executes here, in this process, and its result is sent back.constagent=newCoderAgent({organizationId: process.env.CODER_ORG_ID!,model: "claude-sonnet-4-6",workspaceId: ws.id,// binds the chat's workspace-scoped toolsinstructions: "Audit the project in the workspace. Use latestVersion to check dependencies.",tools: {latestVersion: tool({description: "Look up the latest published version of an npm package.",inputSchema: z.object({pkg: z.string()}),execute: async({ pkg })=>{constres=awaitfetch(`https://registry.npmjs.org/${encodeURIComponent(pkg)}/latest`);if(!res.ok)return{ pkg,error: `registry returned ${res.status}`};const{ version }=(awaitres.json())as{version: string};return{ pkg, version };},}),},});letreport: string;try{constresult=awaitagent.generate({prompt:
"Read package.json, compare the dependencies against their latest versions, and report on the project's dependency health.",});report=result.text;}finally{awaitagent.archive();// archives the chat; never deletes the workspace}// 3. Provider: schema-constrained extraction through AI Gateway. The provider// takes explicit credentials (its `apiKey` is dual-purpose in BYOK mode).constcoder=createCoder({baseURL: process.env.CODER_URL!,apiKey: process.env.CODER_SESSION_TOKEN!,});const{object: audit}=awaitgenerateObject({model: coder("claude-sonnet-4-6"),schema: z.object({health: z.enum(["good","aging","at-risk"]),outdated: z.array(z.object({pkg: z.string(),current: z.string(),latest: z.string()})),summary: z.string(),}),prompt: `Extract the dependency audit from this report:\n\n${report}`,});console.log(audit.health,audit.summary);console.table(audit.outdated);awaittransport.close();// close cached relay WebSockets on shutdown

Each step stands alone — skip the ones you don't need. For depth on each: ensureCoderWorkspace and workspace creation settings in the sandbox README; custom tools, structured output (when the typed answer must come out of the agent run itself, not a follow-up model call), the workspaces & quota operations guide (fleet sizing, autostop, troubleshooting stuck turns), and the durable-workflow how-to (persisting chatId across job/queue boundaries, drop & timeout recovery) in the agent README; named providers and authentication modes and the enterprise governance & security reference (data flow, credential isolation, audit capture, required permissions) in the provider README.

Contributing

Development setup, the command reference, and how releases work all live in CONTRIBUTING.md. The short version — with mise installed:

mise install && pnpm install # set up the toolchain + dependencies
pnpm check && pnpm test# format check, lint, typecheck, then test

License

Apache-2.0 © Coder Technologies, Inc.

coder/ai-sdk

Coder's integrations with the Vercel AI SDK. Run coding agents inside Coder workspaces, and drive Coder Agents from AI SDK code.

Note

All three packages are pre-1.0 and track experimental upstreams (Coder's chat API is experimental). Expect breaking changes.

Packages

Each package is published to npm independently and ships its own README with full install instructions, usage, and API docs.

Package	Version	What it does
`@coder/ai-sdk-sandbox`		A sandbox provider for the Vercel AI SDK v7 `HarnessAgent`. Runs CLI coding agents — Claude Code, Codex — inside a Coder workspace instead of on the local machine, so each agent gets a real, isolated dev environment with your tools, secrets, and network.
`@coder/ai-sdk-agent`		A Vercel AI SDK–compliant `Agent` (AI SDK v7) backed by Coder Agents, Coder's server-side agent runtime. `new CoderAgent()` returns a real `Agent` — `generate()`, `stream()`, tool calls, the whole interface.
`@coder/ai-sdk-provider`		A Vercel AI SDK provider that routes `generateText` / `streamText` calls through your Coder deployment's AI Gateway. Point it at your deployment with a Coder API token and use any model it proxies — no raw provider keys, with per-user auth and audit.

Experimental: @coder/ai-sdk-effect bridges these packages to Effect (unpublished Phase 1 spike, see #144).

Which package? Need a model (text, streaming, or schema‑constrained structured output) through your deployment → @coder/ai-sdk-provider. Need Coder's server‑side agent (multi‑step tool loop, MCP, workspace file/shell tools) → @coder/ai-sdk-agent. Need to run a CLI coding agent (Claude Code, Codex) inside a workspace → @coder/ai-sdk-sandbox.

Using them together

The packages are independent, but they compose into one application against one deployment, authenticated by one Coder token: provision a workspace with the sandbox package, drive Coder's server-side agent in it with the agent package, then extract a typed result with the provider. The full flow below audits a project's dependencies — the agent works inside the workspace (calling one custom tool that executes in your process), and the provider parses the prose report into a typed object through AI Gateway.

pnpm add @coder/ai-sdk-sandbox @coder/ai-sdk-agent @coder/ai-sdk-provider ai zod
pnpm add @ai-sdk/harness @ai-sdk/provider-utils # peer dependencies of the sandbox packageexport CODER_URL=https://coder.example.com
export CODER_SESSION_TOKEN=$(coder tokens create --name compose-example)export CODER_ORG_ID=<org-uuid># e.g. the first `organization_ids` entry from /api/v2/users/me

import{generateObject,tool}from"ai";import{z}from"zod";import{CoderNativeTransport,ensureCoderWorkspace}from"@coder/ai-sdk-sandbox";import{CoderAgent}from"@coder/ai-sdk-agent";import{createCoder}from"@coder/ai-sdk-provider";// The sandbox transport and the agent both default their connection from the// CODER_URL + CODER_SESSION_TOKEN exported above (explicit `url`/`baseUrl` and// `token` options remain available).// 1. Sandbox: get-or-create a workspace and wait until its agent is ready.// The native transport talks straight to your deployment — no `coder` CLI// or `ssh` on the host. Assumes the template checks out your project.consttransport=newCoderNativeTransport();constws=awaitensureCoderWorkspace({workspace: "dep-audit",create: {template: "docker"},
transport,});if(ws.id===undefined)thrownewError("transport did not report a workspace id");// 2. Agent: drive Coder's server-side agent loop in that workspace. The// server runs the multi-step loop and its file/shell tools; your custom// tool executes here, in this process, and its result is sent back.constagent=newCoderAgent({organizationId: process.env.CODER_ORG_ID!,model: "claude-sonnet-4-6",workspaceId: ws.id,// binds the chat's workspace-scoped toolsinstructions: "Audit the project in the workspace. Use latestVersion to check dependencies.",tools: {latestVersion: tool({description: "Look up the latest published version of an npm package.",inputSchema: z.object({pkg: z.string()}),execute: async({ pkg })=>{constres=awaitfetch(`https://registry.npmjs.org/${encodeURIComponent(pkg)}/latest`);if(!res.ok)return{ pkg,error: `registry returned ${res.status}`};const{ version }=(awaitres.json())as{version: string};return{ pkg, version };},}),},});letreport: string;try{constresult=awaitagent.generate({prompt:
"Read package.json, compare the dependencies against their latest versions, and report on the project's dependency health.",});report=result.text;}finally{awaitagent.archive();// archives the chat; never deletes the workspace}// 3. Provider: schema-constrained extraction through AI Gateway. The provider// takes explicit credentials (its `apiKey` is dual-purpose in BYOK mode).constcoder=createCoder({baseURL: process.env.CODER_URL!,apiKey: process.env.CODER_SESSION_TOKEN!,});const{object: audit}=awaitgenerateObject({model: coder("claude-sonnet-4-6"),schema: z.object({health: z.enum(["good","aging","at-risk"]),outdated: z.array(z.object({pkg: z.string(),current: z.string(),latest: z.string()})),summary: z.string(),}),prompt: `Extract the dependency audit from this report:\n\n${report}`,});console.log(audit.health,audit.summary);console.table(audit.outdated);awaittransport.close();// close cached relay WebSockets on shutdown

Each step stands alone — skip the ones you don't need. For depth on each: ensureCoderWorkspace and workspace creation settings in the sandbox README; custom tools, structured output (when the typed answer must come out of the agent run itself, not a follow-up model call), the workspaces & quota operations guide (fleet sizing, autostop, troubleshooting stuck turns), and the durable-workflow how-to (persisting chatId across job/queue boundaries, drop & timeout recovery) in the agent README; named providers and authentication modes and the enterprise governance & security reference (data flow, credential isolation, audit capture, required permissions) in the provider README.

Contributing

Development setup, the command reference, and how releases work all live in CONTRIBUTING.md. The short version — with mise installed:

mise install && pnpm install # set up the toolchain + dependencies
pnpm check && pnpm test# format check, lint, typecheck, then test

License

Apache-2.0 © Coder Technologies, Inc.

coder/ai-sdk

Coder's integrations with the Vercel AI SDK. Run coding agents inside Coder workspaces, and drive Coder Agents from AI SDK code.

Note

All three packages are pre-1.0 and track experimental upstreams (Coder's chat API is experimental). Expect breaking changes.

Packages

Each package is published to npm independently and ships its own README with full install instructions, usage, and API docs.

Package	Version	What it does
`@coder/ai-sdk-sandbox`		A sandbox provider for the Vercel AI SDK v7 `HarnessAgent`. Runs CLI coding agents — Claude Code, Codex — inside a Coder workspace instead of on the local machine, so each agent gets a real, isolated dev environment with your tools, secrets, and network.
`@coder/ai-sdk-agent`		A Vercel AI SDK–compliant `Agent` (AI SDK v7) backed by Coder Agents, Coder's server-side agent runtime. `new CoderAgent()` returns a real `Agent` — `generate()`, `stream()`, tool calls, the whole interface.
`@coder/ai-sdk-provider`		A Vercel AI SDK provider that routes `generateText` / `streamText` calls through your Coder deployment's AI Gateway. Point it at your deployment with a Coder API token and use any model it proxies — no raw provider keys, with per-user auth and audit.

Experimental: @coder/ai-sdk-effect bridges these packages to Effect (unpublished Phase 1 spike, see #144).

Which package? Need a model (text, streaming, or schema‑constrained structured output) through your deployment → @coder/ai-sdk-provider. Need Coder's server‑side agent (multi‑step tool loop, MCP, workspace file/shell tools) → @coder/ai-sdk-agent. Need to run a CLI coding agent (Claude Code, Codex) inside a workspace → @coder/ai-sdk-sandbox.

Using them together

The packages are independent, but they compose into one application against one deployment, authenticated by one Coder token: provision a workspace with the sandbox package, drive Coder's server-side agent in it with the agent package, then extract a typed result with the provider. The full flow below audits a project's dependencies — the agent works inside the workspace (calling one custom tool that executes in your process), and the provider parses the prose report into a typed object through AI Gateway.

pnpm add @coder/ai-sdk-sandbox @coder/ai-sdk-agent @coder/ai-sdk-provider ai zod
pnpm add @ai-sdk/harness @ai-sdk/provider-utils # peer dependencies of the sandbox packageexport CODER_URL=https://coder.example.com
export CODER_SESSION_TOKEN=$(coder tokens create --name compose-example)export CODER_ORG_ID=<org-uuid># e.g. the first `organization_ids` entry from /api/v2/users/me

import{generateObject,tool}from"ai";import{z}from"zod";import{CoderNativeTransport,ensureCoderWorkspace}from"@coder/ai-sdk-sandbox";import{CoderAgent}from"@coder/ai-sdk-agent";import{createCoder}from"@coder/ai-sdk-provider";// The sandbox transport and the agent both default their connection from the// CODER_URL + CODER_SESSION_TOKEN exported above (explicit `url`/`baseUrl` and// `token` options remain available).// 1. Sandbox: get-or-create a workspace and wait until its agent is ready.// The native transport talks straight to your deployment — no `coder` CLI// or `ssh` on the host. Assumes the template checks out your project.consttransport=newCoderNativeTransport();constws=awaitensureCoderWorkspace({workspace: "dep-audit",create: {template: "docker"},
transport,});if(ws.id===undefined)thrownewError("transport did not report a workspace id");// 2. Agent: drive Coder's server-side agent loop in that workspace. The// server runs the multi-step loop and its file/shell tools; your custom// tool executes here, in this process, and its result is sent back.constagent=newCoderAgent({organizationId: process.env.CODER_ORG_ID!,model: "claude-sonnet-4-6",workspaceId: ws.id,// binds the chat's workspace-scoped toolsinstructions: "Audit the project in the workspace. Use latestVersion to check dependencies.",tools: {latestVersion: tool({description: "Look up the latest published version of an npm package.",inputSchema: z.object({pkg: z.string()}),execute: async({ pkg })=>{constres=awaitfetch(`https://registry.npmjs.org/${encodeURIComponent(pkg)}/latest`);if(!res.ok)return{ pkg,error: `registry returned ${res.status}`};const{ version }=(awaitres.json())as{version: string};return{ pkg, version };},}),},});letreport: string;try{constresult=awaitagent.generate({prompt:
"Read package.json, compare the dependencies against their latest versions, and report on the project's dependency health.",});report=result.text;}finally{awaitagent.archive();// archives the chat; never deletes the workspace}// 3. Provider: schema-constrained extraction through AI Gateway. The provider// takes explicit credentials (its `apiKey` is dual-purpose in BYOK mode).constcoder=createCoder({baseURL: process.env.CODER_URL!,apiKey: process.env.CODER_SESSION_TOKEN!,});const{object: audit}=awaitgenerateObject({model: coder("claude-sonnet-4-6"),schema: z.object({health: z.enum(["good","aging","at-risk"]),outdated: z.array(z.object({pkg: z.string(),current: z.string(),latest: z.string()})),summary: z.string(),}),prompt: `Extract the dependency audit from this report:\n\n${report}`,});console.log(audit.health,audit.summary);console.table(audit.outdated);awaittransport.close();// close cached relay WebSockets on shutdown

Each step stands alone — skip the ones you don't need. For depth on each: ensureCoderWorkspace and workspace creation settings in the sandbox README; custom tools, structured output (when the typed answer must come out of the agent run itself, not a follow-up model call), the workspaces & quota operations guide (fleet sizing, autostop, troubleshooting stuck turns), and the durable-workflow how-to (persisting chatId across job/queue boundaries, drop & timeout recovery) in the agent README; named providers and authentication modes and the enterprise governance & security reference (data flow, credential isolation, audit capture, required permissions) in the provider README.

Contributing

Development setup, the command reference, and how releases work all live in CONTRIBUTING.md. The short version — with mise installed:

mise install && pnpm install # set up the toolchain + dependencies
pnpm check && pnpm test# format check, lint, typecheck, then test

License

Apache-2.0 © Coder Technologies, Inc.

coder/ai-sdk

Coder's integrations with the Vercel AI SDK. Run coding agents inside Coder workspaces, and drive Coder Agents from AI SDK code.

Note

All three packages are pre-1.0 and track experimental upstreams (Coder's chat API is experimental). Expect breaking changes.

Packages

Each package is published to npm independently and ships its own README with full install instructions, usage, and API docs.

Package	Version	What it does
`@coder/ai-sdk-sandbox`		A sandbox provider for the Vercel AI SDK v7 `HarnessAgent`. Runs CLI coding agents — Claude Code, Codex — inside a Coder workspace instead of on the local machine, so each agent gets a real, isolated dev environment with your tools, secrets, and network.
`@coder/ai-sdk-agent`		A Vercel AI SDK–compliant `Agent` (AI SDK v7) backed by Coder Agents, Coder's server-side agent runtime. `new CoderAgent()` returns a real `Agent` — `generate()`, `stream()`, tool calls, the whole interface.
`@coder/ai-sdk-provider`		A Vercel AI SDK provider that routes `generateText` / `streamText` calls through your Coder deployment's AI Gateway. Point it at your deployment with a Coder API token and use any model it proxies — no raw provider keys, with per-user auth and audit.

Experimental: @coder/ai-sdk-effect bridges these packages to Effect (unpublished Phase 1 spike, see #144).

Which package? Need a model (text, streaming, or schema‑constrained structured output) through your deployment → @coder/ai-sdk-provider. Need Coder's server‑side agent (multi‑step tool loop, MCP, workspace file/shell tools) → @coder/ai-sdk-agent. Need to run a CLI coding agent (Claude Code, Codex) inside a workspace → @coder/ai-sdk-sandbox.

Using them together

The packages are independent, but they compose into one application against one deployment, authenticated by one Coder token: provision a workspace with the sandbox package, drive Coder's server-side agent in it with the agent package, then extract a typed result with the provider. The full flow below audits a project's dependencies — the agent works inside the workspace (calling one custom tool that executes in your process), and the provider parses the prose report into a typed object through AI Gateway.

pnpm add @coder/ai-sdk-sandbox @coder/ai-sdk-agent @coder/ai-sdk-provider ai zod
pnpm add @ai-sdk/harness @ai-sdk/provider-utils # peer dependencies of the sandbox packageexport CODER_URL=https://coder.example.com
export CODER_SESSION_TOKEN=$(coder tokens create --name compose-example)export CODER_ORG_ID=<org-uuid># e.g. the first `organization_ids` entry from /api/v2/users/me

import{generateObject,tool}from"ai";import{z}from"zod";import{CoderNativeTransport,ensureCoderWorkspace}from"@coder/ai-sdk-sandbox";import{CoderAgent}from"@coder/ai-sdk-agent";import{createCoder}from"@coder/ai-sdk-provider";// The sandbox transport and the agent both default their connection from the// CODER_URL + CODER_SESSION_TOKEN exported above (explicit `url`/`baseUrl` and// `token` options remain available).// 1. Sandbox: get-or-create a workspace and wait until its agent is ready.// The native transport talks straight to your deployment — no `coder` CLI// or `ssh` on the host. Assumes the template checks out your project.consttransport=newCoderNativeTransport();constws=awaitensureCoderWorkspace({workspace: "dep-audit",create: {template: "docker"},
transport,});if(ws.id===undefined)thrownewError("transport did not report a workspace id");// 2. Agent: drive Coder's server-side agent loop in that workspace. The// server runs the multi-step loop and its file/shell tools; your custom// tool executes here, in this process, and its result is sent back.constagent=newCoderAgent({organizationId: process.env.CODER_ORG_ID!,model: "claude-sonnet-4-6",workspaceId: ws.id,// binds the chat's workspace-scoped toolsinstructions: "Audit the project in the workspace. Use latestVersion to check dependencies.",tools: {latestVersion: tool({description: "Look up the latest published version of an npm package.",inputSchema: z.object({pkg: z.string()}),execute: async({ pkg })=>{constres=awaitfetch(`https://registry.npmjs.org/${encodeURIComponent(pkg)}/latest`);if(!res.ok)return{ pkg,error: `registry returned ${res.status}`};const{ version }=(awaitres.json())as{version: string};return{ pkg, version };},}),},});letreport: string;try{constresult=awaitagent.generate({prompt:
"Read package.json, compare the dependencies against their latest versions, and report on the project's dependency health.",});report=result.text;}finally{awaitagent.archive();// archives the chat; never deletes the workspace}// 3. Provider: schema-constrained extraction through AI Gateway. The provider// takes explicit credentials (its `apiKey` is dual-purpose in BYOK mode).constcoder=createCoder({baseURL: process.env.CODER_URL!,apiKey: process.env.CODER_SESSION_TOKEN!,});const{object: audit}=awaitgenerateObject({model: coder("claude-sonnet-4-6"),schema: z.object({health: z.enum(["good","aging","at-risk"]),outdated: z.array(z.object({pkg: z.string(),current: z.string(),latest: z.string()})),summary: z.string(),}),prompt: `Extract the dependency audit from this report:\n\n${report}`,});console.log(audit.health,audit.summary);console.table(audit.outdated);awaittransport.close();// close cached relay WebSockets on shutdown

Each step stands alone — skip the ones you don't need. For depth on each: ensureCoderWorkspace and workspace creation settings in the sandbox README; custom tools, structured output (when the typed answer must come out of the agent run itself, not a follow-up model call), the workspaces & quota operations guide (fleet sizing, autostop, troubleshooting stuck turns), and the durable-workflow how-to (persisting chatId across job/queue boundaries, drop & timeout recovery) in the agent README; named providers and authentication modes and the enterprise governance & security reference (data flow, credential isolation, audit capture, required permissions) in the provider README.

Contributing

Development setup, the command reference, and how releases work all live in CONTRIBUTING.md. The short version — with mise installed:

mise install && pnpm install # set up the toolchain + dependencies
pnpm check && pnpm test# format check, lint, typecheck, then test

License

Apache-2.0 © Coder Technologies, Inc.

coder/ai-sdk

Coder's integrations with the Vercel AI SDK. Run coding agents inside Coder workspaces, and drive Coder Agents from AI SDK code.

Note

All three packages are pre-1.0 and track experimental upstreams (Coder's chat API is experimental). Expect breaking changes.

Packages

Each package is published to npm independently and ships its own README with full install instructions, usage, and API docs.

Package	Version	What it does
`@coder/ai-sdk-sandbox`		A sandbox provider for the Vercel AI SDK v7 `HarnessAgent`. Runs CLI coding agents — Claude Code, Codex — inside a Coder workspace instead of on the local machine, so each agent gets a real, isolated dev environment with your tools, secrets, and network.
`@coder/ai-sdk-agent`		A Vercel AI SDK–compliant `Agent` (AI SDK v7) backed by Coder Agents, Coder's server-side agent runtime. `new CoderAgent()` returns a real `Agent` — `generate()`, `stream()`, tool calls, the whole interface.
`@coder/ai-sdk-provider`		A Vercel AI SDK provider that routes `generateText` / `streamText` calls through your Coder deployment's AI Gateway. Point it at your deployment with a Coder API token and use any model it proxies — no raw provider keys, with per-user auth and audit.

Experimental: @coder/ai-sdk-effect bridges these packages to Effect (unpublished Phase 1 spike, see #144).

Which package? Need a model (text, streaming, or schema‑constrained structured output) through your deployment → @coder/ai-sdk-provider. Need Coder's server‑side agent (multi‑step tool loop, MCP, workspace file/shell tools) → @coder/ai-sdk-agent. Need to run a CLI coding agent (Claude Code, Codex) inside a workspace → @coder/ai-sdk-sandbox.

Using them together

The packages are independent, but they compose into one application against one deployment, authenticated by one Coder token: provision a workspace with the sandbox package, drive Coder's server-side agent in it with the agent package, then extract a typed result with the provider. The full flow below audits a project's dependencies — the agent works inside the workspace (calling one custom tool that executes in your process), and the provider parses the prose report into a typed object through AI Gateway.

pnpm add @coder/ai-sdk-sandbox @coder/ai-sdk-agent @coder/ai-sdk-provider ai zod
pnpm add @ai-sdk/harness @ai-sdk/provider-utils # peer dependencies of the sandbox packageexport CODER_URL=https://coder.example.com
export CODER_SESSION_TOKEN=$(coder tokens create --name compose-example)export CODER_ORG_ID=<org-uuid># e.g. the first `organization_ids` entry from /api/v2/users/me

import{generateObject,tool}from"ai";import{z}from"zod";import{CoderNativeTransport,ensureCoderWorkspace}from"@coder/ai-sdk-sandbox";import{CoderAgent}from"@coder/ai-sdk-agent";import{createCoder}from"@coder/ai-sdk-provider";// The sandbox transport and the agent both default their connection from the// CODER_URL + CODER_SESSION_TOKEN exported above (explicit `url`/`baseUrl` and// `token` options remain available).// 1. Sandbox: get-or-create a workspace and wait until its agent is ready.// The native transport talks straight to your deployment — no `coder` CLI// or `ssh` on the host. Assumes the template checks out your project.consttransport=newCoderNativeTransport();constws=awaitensureCoderWorkspace({workspace: "dep-audit",create: {template: "docker"},
transport,});if(ws.id===undefined)thrownewError("transport did not report a workspace id");// 2. Agent: drive Coder's server-side agent loop in that workspace. The// server runs the multi-step loop and its file/shell tools; your custom// tool executes here, in this process, and its result is sent back.constagent=newCoderAgent({organizationId: process.env.CODER_ORG_ID!,model: "claude-sonnet-4-6",workspaceId: ws.id,// binds the chat's workspace-scoped toolsinstructions: "Audit the project in the workspace. Use latestVersion to check dependencies.",tools: {latestVersion: tool({description: "Look up the latest published version of an npm package.",inputSchema: z.object({pkg: z.string()}),execute: async({ pkg })=>{constres=awaitfetch(`https://registry.npmjs.org/${encodeURIComponent(pkg)}/latest`);if(!res.ok)return{ pkg,error: `registry returned ${res.status}`};const{ version }=(awaitres.json())as{version: string};return{ pkg, version };},}),},});letreport: string;try{constresult=awaitagent.generate({prompt:
"Read package.json, compare the dependencies against their latest versions, and report on the project's dependency health.",});report=result.text;}finally{awaitagent.archive();// archives the chat; never deletes the workspace}// 3. Provider: schema-constrained extraction through AI Gateway. The provider// takes explicit credentials (its `apiKey` is dual-purpose in BYOK mode).constcoder=createCoder({baseURL: process.env.CODER_URL!,apiKey: process.env.CODER_SESSION_TOKEN!,});const{object: audit}=awaitgenerateObject({model: coder("claude-sonnet-4-6"),schema: z.object({health: z.enum(["good","aging","at-risk"]),outdated: z.array(z.object({pkg: z.string(),current: z.string(),latest: z.string()})),summary: z.string(),}),prompt: `Extract the dependency audit from this report:\n\n${report}`,});console.log(audit.health,audit.summary);console.table(audit.outdated);awaittransport.close();// close cached relay WebSockets on shutdown

Each step stands alone — skip the ones you don't need. For depth on each: ensureCoderWorkspace and workspace creation settings in the sandbox README; custom tools, structured output (when the typed answer must come out of the agent run itself, not a follow-up model call), the workspaces & quota operations guide (fleet sizing, autostop, troubleshooting stuck turns), and the durable-workflow how-to (persisting chatId across job/queue boundaries, drop & timeout recovery) in the agent README; named providers and authentication modes and the enterprise governance & security reference (data flow, credential isolation, audit capture, required permissions) in the provider README.

Contributing

Development setup, the command reference, and how releases work all live in CONTRIBUTING.md. The short version — with mise installed:

mise install && pnpm install # set up the toolchain + dependencies
pnpm check && pnpm test# format check, lint, typecheck, then test

License

coder/ai-sdk

Coder's integrations with the Vercel AI SDK. Run coding agents inside Coder workspaces, and drive Coder Agents from AI SDK code.

Note

All three packages are pre-1.0 and track experimental upstreams (Coder's chat API is experimental). Expect breaking changes.

Packages

Each package is published to npm independently and ships its own README with full install instructions, usage, and API docs.

Package	Version	What it does
`@coder/ai-sdk-sandbox`		A sandbox provider for the Vercel AI SDK v7 `HarnessAgent`. Runs CLI coding agents — Claude Code, Codex — inside a Coder workspace instead of on the local machine, so each agent gets a real, isolated dev environment with your tools, secrets, and network.
`@coder/ai-sdk-agent`		A Vercel AI SDK–compliant `Agent` (AI SDK v7) backed by Coder Agents, Coder's server-side agent runtime. `new CoderAgent()` returns a real `Agent` — `generate()`, `stream()`, tool calls, the whole interface.
`@coder/ai-sdk-provider`		A Vercel AI SDK provider that routes `generateText` / `streamText` calls through your Coder deployment's AI Gateway. Point it at your deployment with a Coder API token and use any model it proxies — no raw provider keys, with per-user auth and audit.

Experimental: @coder/ai-sdk-effect bridges these packages to Effect (unpublished Phase 1 spike, see #144).

Which package? Need a model (text, streaming, or schema‑constrained structured output) through your deployment → @coder/ai-sdk-provider. Need Coder's server‑side agent (multi‑step tool loop, MCP, workspace file/shell tools) → @coder/ai-sdk-agent. Need to run a CLI coding agent (Claude Code, Codex) inside a workspace → @coder/ai-sdk-sandbox.

Using them together

The packages are independent, but they compose into one application against one deployment, authenticated by one Coder token: provision a workspace with the sandbox package, drive Coder's server-side agent in it with the agent package, then extract a typed result with the provider. The full flow below audits a project's dependencies — the agent works inside the workspace (calling one custom tool that executes in your process), and the provider parses the prose report into a typed object through AI Gateway.

pnpm add @coder/ai-sdk-sandbox @coder/ai-sdk-agent @coder/ai-sdk-provider ai zod
pnpm add @ai-sdk/harness @ai-sdk/provider-utils # peer dependencies of the sandbox packageexport CODER_URL=https://coder.example.com
export CODER_SESSION_TOKEN=$(coder tokens create --name compose-example)export CODER_ORG_ID=<org-uuid># e.g. the first `organization_ids` entry from /api/v2/users/me

import{generateObject,tool}from"ai";import{z}from"zod";import{CoderNativeTransport,ensureCoderWorkspace}from"@coder/ai-sdk-sandbox";import{CoderAgent}from"@coder/ai-sdk-agent";import{createCoder}from"@coder/ai-sdk-provider";// The sandbox transport and the agent both default their connection from the// CODER_URL + CODER_SESSION_TOKEN exported above (explicit `url`/`baseUrl` and// `token` options remain available).// 1. Sandbox: get-or-create a workspace and wait until its agent is ready.// The native transport talks straight to your deployment — no `coder` CLI// or `ssh` on the host. Assumes the template checks out your project.consttransport=newCoderNativeTransport();constws=awaitensureCoderWorkspace({workspace: "dep-audit",create: {template: "docker"},
transport,});if(ws.id===undefined)thrownewError("transport did not report a workspace id");// 2. Agent: drive Coder's server-side agent loop in that workspace. The// server runs the multi-step loop and its file/shell tools; your custom// tool executes here, in this process, and its result is sent back.constagent=newCoderAgent({organizationId: process.env.CODER_ORG_ID!,model: "claude-sonnet-4-6",workspaceId: ws.id,// binds the chat's workspace-scoped toolsinstructions: "Audit the project in the workspace. Use latestVersion to check dependencies.",tools: {latestVersion: tool({description: "Look up the latest published version of an npm package.",inputSchema: z.object({pkg: z.string()}),execute: async({ pkg })=>{constres=awaitfetch(`https://registry.npmjs.org/${encodeURIComponent(pkg)}/latest`);if(!res.ok)return{ pkg,error: `registry returned ${res.status}`};const{ version }=(awaitres.json())as{version: string};return{ pkg, version };},}),},});letreport: string;try{constresult=awaitagent.generate({prompt:
"Read package.json, compare the dependencies against their latest versions, and report on the project's dependency health.",});report=result.text;}finally{awaitagent.archive();// archives the chat; never deletes the workspace}// 3. Provider: schema-constrained extraction through AI Gateway. The provider// takes explicit credentials (its `apiKey` is dual-purpose in BYOK mode).constcoder=createCoder({baseURL: process.env.CODER_URL!,apiKey: process.env.CODER_SESSION_TOKEN!,});const{object: audit}=awaitgenerateObject({model: coder("claude-sonnet-4-6"),schema: z.object({health: z.enum(["good","aging","at-risk"]),outdated: z.array(z.object({pkg: z.string(),current: z.string(),latest: z.string()})),summary: z.string(),}),prompt: `Extract the dependency audit from this report:\n\n${report}`,});console.log(audit.health,audit.summary);console.table(audit.outdated);awaittransport.close();// close cached relay WebSockets on shutdown

Each step stands alone — skip the ones you don't need. For depth on each: ensureCoderWorkspace and workspace creation settings in the sandbox README; custom tools, structured output (when the typed answer must come out of the agent run itself, not a follow-up model call), the workspaces & quota operations guide (fleet sizing, autostop, troubleshooting stuck turns), and the durable-workflow how-to (persisting chatId across job/queue boundaries, drop & timeout recovery) in the agent README; named providers and authentication modes and the enterprise governance & security reference (data flow, credential isolation, audit capture, required permissions) in the provider README.

Contributing

Development setup, the command reference, and how releases work all live in CONTRIBUTING.md. The short version — with mise installed:

mise install && pnpm install # set up the toolchain + dependencies
pnpm check && pnpm test# format check, lint, typecheck, then test

License

coder/ai-sdk

Coder's integrations with the Vercel AI SDK. Run coding agents inside Coder workspaces, and drive Coder Agents from AI SDK code.

Note

All three packages are pre-1.0 and track experimental upstreams (Coder's chat API is experimental). Expect breaking changes.

Packages

Each package is published to npm independently and ships its own README with full install instructions, usage, and API docs.

Package	Version	What it does
`@coder/ai-sdk-sandbox`		A sandbox provider for the Vercel AI SDK v7 `HarnessAgent`. Runs CLI coding agents — Claude Code, Codex — inside a Coder workspace instead of on the local machine, so each agent gets a real, isolated dev environment with your tools, secrets, and network.
`@coder/ai-sdk-agent`		A Vercel AI SDK–compliant `Agent` (AI SDK v7) backed by Coder Agents, Coder's server-side agent runtime. `new CoderAgent()` returns a real `Agent` — `generate()`, `stream()`, tool calls, the whole interface.
`@coder/ai-sdk-provider`		A Vercel AI SDK provider that routes `generateText` / `streamText` calls through your Coder deployment's AI Gateway. Point it at your deployment with a Coder API token and use any model it proxies — no raw provider keys, with per-user auth and audit.

Experimental: @coder/ai-sdk-effect bridges these packages to Effect (unpublished Phase 1 spike, see #144).

Which package? Need a model (text, streaming, or schema‑constrained structured output) through your deployment → @coder/ai-sdk-provider. Need Coder's server‑side agent (multi‑step tool loop, MCP, workspace file/shell tools) → @coder/ai-sdk-agent. Need to run a CLI coding agent (Claude Code, Codex) inside a workspace → @coder/ai-sdk-sandbox.

Using them together

The packages are independent, but they compose into one application against one deployment, authenticated by one Coder token: provision a workspace with the sandbox package, drive Coder's server-side agent in it with the agent package, then extract a typed result with the provider. The full flow below audits a project's dependencies — the agent works inside the workspace (calling one custom tool that executes in your process), and the provider parses the prose report into a typed object through AI Gateway.

pnpm add @coder/ai-sdk-sandbox @coder/ai-sdk-agent @coder/ai-sdk-provider ai zod
pnpm add @ai-sdk/harness @ai-sdk/provider-utils # peer dependencies of the sandbox packageexport CODER_URL=https://coder.example.com
export CODER_SESSION_TOKEN=$(coder tokens create --name compose-example)export CODER_ORG_ID=<org-uuid># e.g. the first `organization_ids` entry from /api/v2/users/me

import{generateObject,tool}from"ai";import{z}from"zod";import{CoderNativeTransport,ensureCoderWorkspace}from"@coder/ai-sdk-sandbox";import{CoderAgent}from"@coder/ai-sdk-agent";import{createCoder}from"@coder/ai-sdk-provider";// The sandbox transport and the agent both default their connection from the// CODER_URL + CODER_SESSION_TOKEN exported above (explicit `url`/`baseUrl` and// `token` options remain available).// 1. Sandbox: get-or-create a workspace and wait until its agent is ready.// The native transport talks straight to your deployment — no `coder` CLI// or `ssh` on the host. Assumes the template checks out your project.consttransport=newCoderNativeTransport();constws=awaitensureCoderWorkspace({workspace: "dep-audit",create: {template: "docker"},
transport,});if(ws.id===undefined)thrownewError("transport did not report a workspace id");// 2. Agent: drive Coder's server-side agent loop in that workspace. The// server runs the multi-step loop and its file/shell tools; your custom// tool executes here, in this process, and its result is sent back.constagent=newCoderAgent({organizationId: process.env.CODER_ORG_ID!,model: "claude-sonnet-4-6",workspaceId: ws.id,// binds the chat's workspace-scoped toolsinstructions: "Audit the project in the workspace. Use latestVersion to check dependencies.",tools: {latestVersion: tool({description: "Look up the latest published version of an npm package.",inputSchema: z.object({pkg: z.string()}),execute: async({ pkg })=>{constres=awaitfetch(`https://registry.npmjs.org/${encodeURIComponent(pkg)}/latest`);if(!res.ok)return{ pkg,error: `registry returned ${res.status}`};const{ version }=(awaitres.json())as{version: string};return{ pkg, version };},}),},});letreport: string;try{constresult=awaitagent.generate({prompt:
"Read package.json, compare the dependencies against their latest versions, and report on the project's dependency health.",});report=result.text;}finally{awaitagent.archive();// archives the chat; never deletes the workspace}// 3. Provider: schema-constrained extraction through AI Gateway. The provider// takes explicit credentials (its `apiKey` is dual-purpose in BYOK mode).constcoder=createCoder({baseURL: process.env.CODER_URL!,apiKey: process.env.CODER_SESSION_TOKEN!,});const{object: audit}=awaitgenerateObject({model: coder("claude-sonnet-4-6"),schema: z.object({health: z.enum(["good","aging","at-risk"]),outdated: z.array(z.object({pkg: z.string(),current: z.string(),latest: z.string()})),summary: z.string(),}),prompt: `Extract the dependency audit from this report:\n\n${report}`,});console.log(audit.health,audit.summary);console.table(audit.outdated);awaittransport.close();// close cached relay WebSockets on shutdown

Each step stands alone — skip the ones you don't need. For depth on each: ensureCoderWorkspace and workspace creation settings in the sandbox README; custom tools, structured output (when the typed answer must come out of the agent run itself, not a follow-up model call), the workspaces & quota operations guide (fleet sizing, autostop, troubleshooting stuck turns), and the durable-workflow how-to (persisting chatId across job/queue boundaries, drop & timeout recovery) in the agent README; named providers and authentication modes and the enterprise governance & security reference (data flow, credential isolation, audit capture, required permissions) in the provider README.

Contributing

Development setup, the command reference, and how releases work all live in CONTRIBUTING.md. The short version — with mise installed:

mise install && pnpm install # set up the toolchain + dependencies
pnpm check && pnpm test# format check, lint, typecheck, then test

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
packages		packages
tools/oxlint/anti-slop		tools/oxlint/anti-slop
.editorconfig		.editorconfig
.gitignore		.gitignore
.oxfmtrc.json		.oxfmtrc.json
.oxlintrc.json		.oxlintrc.json
.release-please-manifest.json		.release-please-manifest.json
AGENTS.md		AGENTS.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
mise.lock		mise.lock
mise.toml		mise.toml
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
release-please-config.json		release-please-config.json
tsconfig.base.json		tsconfig.base.json

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
packages		packages
tools/oxlint/anti-slop		tools/oxlint/anti-slop
.editorconfig		.editorconfig
.gitignore		.gitignore
.oxfmtrc.json		.oxfmtrc.json
.oxlintrc.json		.oxlintrc.json
.release-please-manifest.json		.release-please-manifest.json
AGENTS.md		AGENTS.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
mise.lock		mise.lock
mise.toml		mise.toml
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
release-please-config.json		release-please-config.json
tsconfig.base.json		tsconfig.base.json

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
packages		packages
tools/oxlint/anti-slop		tools/oxlint/anti-slop
.editorconfig		.editorconfig
.gitignore		.gitignore
.oxfmtrc.json		.oxfmtrc.json
.oxlintrc.json		.oxlintrc.json
.release-please-manifest.json		.release-please-manifest.json
AGENTS.md		AGENTS.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
mise.lock		mise.lock
mise.toml		mise.toml
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
release-please-config.json		release-please-config.json
tsconfig.base.json		tsconfig.base.json

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
packages		packages
tools/oxlint/anti-slop		tools/oxlint/anti-slop
.editorconfig		.editorconfig
.gitignore		.gitignore
.oxfmtrc.json		.oxfmtrc.json
.oxlintrc.json		.oxlintrc.json
.release-please-manifest.json		.release-please-manifest.json
AGENTS.md		AGENTS.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
mise.lock		mise.lock
mise.toml		mise.toml
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
release-please-config.json		release-please-config.json
tsconfig.base.json		tsconfig.base.json

Name		Name	Last commit message	Last commit date
.github/workflows		.github/workflows
packages		packages
tools/oxlint/anti-slop		tools/oxlint/anti-slop
.editorconfig		.editorconfig
.gitignore		.gitignore
.oxfmtrc.json		.oxfmtrc.json
.oxlintrc.json		.oxlintrc.json
.release-please-manifest.json		.release-please-manifest.json
AGENTS.md		AGENTS.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
mise.lock		mise.lock
mise.toml		mise.toml
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
release-please-config.json		release-please-config.json
tsconfig.base.json		tsconfig.base.json

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

coder/ai-sdk

Packages

Using them together

Contributing

License

About

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

coder/ai-sdk

Packages

Using them together

Contributing

License

About

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

coder/ai-sdk

Packages

Using them together

Contributing

License

About

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages

Uh oh!

Latest commit

History

Folders and files

Repository files navigation

coder/ai-sdk

Packages

Using them together

Contributing

License

About