feat(opencode-workspaces-plugin): add Daytona workspace adaptor plugin for OpenCode

[jamesmurdza]

Description

Adds apps/opencode-workspaces-plugin: an OpenCode plugin that provisions Daytona sandboxes as remote workspaces via OpenCode's experimental workspace-adaptor API.

This PR was originally ported from daytonaio/daytona#4504, with Nx build config replaced by the standalone npm layout used elsewhere in this repo, and fixing several issues in the original plugin. It is not published and does not change packages/opencode-plugin.

This app has extensive test coverage, including end-to-end tests that run a full user flow in the actual OpenCode TUI with the plugin installed.

Upstream bugs in OpenCode

To make this PR work, two PRs were raised in OpenCode:

• fix(server): don't forward host directory to remote workspace anomalyco/opencode#40136 — the actual fix: strips the directory query param before proxying, so the remote falls back to its own project root. Once this ships in a release and the plugin's pinned OPENCODE_VERSION is bumped to include it, the symlink workaround can be removed.
• fix(server): log upstream 5xx bodies from proxied workspace requests anomalyco/opencode#40135 — logs upstream 5xx bodies on the host proxy, making this class of failure (previously an opaque 500 buried in the sandbox) diagnosable from the host log.

These PRs have both been merged and shipped.

Related issue(s)

Scope

• This PR touches no more than one package/app (release routing is by changed file path).
• The PR title follows Conventional Commits
  (e.g. feat(pi-extension): ..., fix(adk-plugin): ...) — it becomes the squash-commit
  message that release-please reads.

Checks

• I ran the affected package's lint/build/test locally and they pass.
• I updated documentation where relevant.

Legal

• Every commit is signed off for the
  DCO (git commit -s); the sign-off matches the
  commit author.
  1 of 15 commits signed off — needs git rebase --signoff main.
• I agree to the
  Contributor License Agreement.
  On my first PR, the CLA assistant will comment and I will reply to sign (once).

[github-actions]

All contributors have signed the CLA. ✅ Thank you!
_{Posted by the CLA Assistant Lite bot.}

[jamesmurdza]

I have read the CLA Document and I hereby sign the CLA

[cubic-dev-ai]

3 issues found across 13 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/opencode-workspaces-plugin/.opencode/plugin/daytona/index.ts">

<violation number="1" location="apps/opencode-workspaces-plugin/.opencode/plugin/daytona/index.ts:208">
P2: Concurrent workspace creates in the same millisecond share this temp directory, causing clone/tar races and cleanup to fail or provision the wrong repository. Use a unique directory from `mkdtemp` before creating the sandbox files.</violation>
</file>

<file name="apps/opencode-workspaces-plugin/test/integration.test.ts">

<violation number="1" location="apps/opencode-workspaces-plugin/test/integration.test.ts:31">
P1: Hardcoded `/tmp/daytona-plugin.log` is shared between `integration.test.ts` and `e2e-tui.test.ts`. If both run concurrently (e.g., parallel CI jobs on the same host) they overwrite each other's logs, causing both tests to miss sandbox names in cleanup and potentially leave orphan sandboxes running. Use a unique path per test file.</violation>

<violation number="2" location="apps/opencode-workspaces-plugin/test/integration.test.ts:248">
P2: Workspace creation fetch is unbounded — if the plugin hangs during provisioning the test freezes until the runner timeout. Add `signal: AbortSignal.timeout(...)`, matching the pattern already used in `waitForServer` for the health check.</violation>
</file>

<sub>Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic</sub>

[cubic-dev-ai]

P1: Hardcoded /tmp/daytona-plugin.log is shared between integration.test.ts and e2e-tui.test.ts. If both run concurrently (e.g., parallel CI jobs on the same host) they overwrite each other's logs, causing both tests to miss sandbox names in cleanup and potentially leave orphan sandboxes running. Use a unique path per test file.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/opencode-workspaces-plugin/test/integration.test.ts, line 31:

<comment>Hardcoded `/tmp/daytona-plugin.log` is shared between `integration.test.ts` and `e2e-tui.test.ts`. If both run concurrently (e.g., parallel CI jobs on the same host) they overwrite each other's logs, causing both tests to miss sandbox names in cleanup and potentially leave orphan sandboxes running. Use a unique path per test file.</comment>

<file context>
@@ -0,0 +1,290 @@
+// The plugin's own debug log. It records every workspace it starts building,
+// which is the only reliable way to know what to clean up when a create call
+// hangs rather than returning. Kept in sync with e2e-tui.test.ts.
+const PLUGIN_LOG = '/tmp/daytona-plugin.log'
+async function readLog(): Promise<string> {
+  return await readFile(PLUGIN_LOG, 'utf8').catch(() => '')
</file context>

[cubic-dev-ai]

P2: Concurrent workspace creates in the same millisecond share this temp directory, causing clone/tar races and cleanup to fail or provision the wrong repository. Use a unique directory from mkdtemp before creating the sandbox files.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/opencode-workspaces-plugin/.opencode/plugin/daytona/index.ts, line 208:

<comment>Concurrent workspace creates in the same millisecond share this temp directory, causing clone/tar races and cleanup to fail or provision the wrong repository. Use a unique directory from `mkdtemp` before creating the sandbox files.</comment>

<file context>
@@ -0,0 +1,366 @@
+        throw new Error('DAYTONA_API_KEY environment variable is not set')
+      }
+
+      const temp = join(tmpdir(), `opencode-daytona-${Date.now()}`)
+      const d = getDaytona()
+      debug(
</file context>

[cubic-dev-ai]

P2: Workspace creation fetch is unbounded — if the plugin hangs during provisioning the test freezes until the runner timeout. Add signal: AbortSignal.timeout(...), matching the pattern already used in waitForServer for the health check.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/opencode-workspaces-plugin/test/integration.test.ts, line 248:

<comment>Workspace creation fetch is unbounded — if the plugin hangs during provisioning the test freezes until the runner timeout. Add `signal: AbortSignal.timeout(...)`, matching the pattern already used in `waitForServer` for the health check.</comment>

<file context>
@@ -0,0 +1,290 @@
+
+  test('creates and deletes workspace via API', async () => {
+    console.log('\n=== Step 4: Create workspace via API ===')
+    const createRes = await fetch(`http://127.0.0.1:${serverPort}/experimental/workspace`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/json' },
</file context>

[mislavivanda]

@jamesmurdza Reviewed the full source and live-tested everything against real Daytona sandboxes (5
workspaces created/destroyed over the session, zero leaks — the partial-create cleanup
demonstrably deletes its sandbox on failure). Typecheck, plugin, and integration suites are
green; the e2e TUI suite passes too, with one environment caveat documented below. Solid
work overall — the create() error path, the bounded health polls, and the log-based test
sweeps all held up under deliberate abuse.

A few requests before merge, all small:

1. Normalize "adaptor" → "adapter"

The upstream API spells it adapter everywhere (WorkspaceAdapter,
/experimental/workspace/adapter, workspace.adapter.list()); the PR mixes both variants,
sometimes in the same file (README's "Adaptor registration" section curls
/workspace/adapter three lines later). Occurrences: daytona/index.ts lines 7, 192
(variable), 360–361; plugin/index.ts line 8; plugin README lines 95, 97, 171, 183;
integration.test.ts line 131; root README table row. Verified the rename typechecks and
tests still pass.

2. README: "Running the e2e on any machine" section

The e2e drives the real TUI, so it inherits the developer's shell and global opencode
config — and fails on machines that differ from a vanilla setup. Both failure modes are
fixable purely via environment, no test changes needed. Verified on a machine where the
test fails as written and passes with:

SHELL=/bin/sh XDG_CONFIG_HOME=$(mktemp -d) npm test -- test/e2e-tui.test.ts

Please add a short README subsection under Running Tests documenting this, with the why:

• SHELL=/bin/sh — the test types cd … && opencode into a fresh tmux pane immediately
  after new-session; heavier shell inits (zsh + plugins) eat part of that line, so the
  TUI silently starts in the wrong directory (plugin log then shows worktree=<repo root>
  instead of the temp project). A plain sh pane has no init to race.
• XDG_CONFIG_HOME=$(mktemp -d) — isolates ~/.config/opencode. With a custom default
  agent configured globally (e.g. an oh-my-opencode setup), the warped session's first
  prompt dies silently on the remote: session created, zero assistant output, zero tokens,
  $0.00, no error surfaced. Isolated A/B on the same machine: vanilla config → reply in
  ~1s; custom default agent → dead session. Auth lives under XDG_DATA, so provider keys
  still forward.
• OPENCODE_SERVER_PASSWORD must be unset — all three suites poll /global/health
  unauthenticated and fail with opaque 401s when it's exported.

The custom-agent behavior itself looks like upstream workspace-API territory (remote can't
resolve host-only agents and swallows the prompt without an error) — worth filing as
feedback to the opencode team alongside the two PRs already linked in the description, and
worth a one-line "known limitation" note in this README.

3. Stale comment: the TUI-render "sync gap"

The e2e header (test/e2e-tui.test.ts:16–20) says OpenCode's global sync delivers state
counts but not message content, so the reply never renders in the host TUI and is only
logged informationally. On 1.18.15 the reply DOES render (the test itself prints "TUI
rendered the reply" now). Suggest updating the comment, and optionally promoting the
informational check to a hard assertion.

4. Minor / documentation

• create() unconditionally overwrites the sandbox repo's opencode.json (index.ts:292–300)
  and strips committed .opencode/ from the upload (index.ts:263) — repos carrying their own
  opencode config lose it remotely. Fine as a v1 trade-off, but worth a README note (or
  merging instructions into an existing config later).
• Only the last commit is uploaded (clone from worktree, --depth 1) — uncommitted changes
  don't travel. Worth one README sentence.
• Provider credentials are forwarded into sandbox envVars (that's how the remote can call
  models) and are visible in the Daytona dashboard — inherent to the design, deserves a
  one-line note.
• PR body is stale: it says "1 of 15 commits signed off", but all commits now carry matching
  Signed-off-by trailers.

On the cubic comments

• Temp-dir Date.now() collision — agreed, mkdtemp is a strict improvement; please take it.
• Unbounded create fetch — already bounded by bun's --timeout 180000 and the afterAll
  log-sweep exists precisely for hung creates; optional, and if added the bound should be
  generous (creates legitimately took 16–50s in live runs).
• Shared plugin log between test files — the path is the plugin's fixed log which tests
  only read (append-only + per-file offsets, files run sequentially), so the described
  orphan scenario can't occur; making the plugin's log path env-configurable would be nice
  future polish but isn't needed for merge.