Threads is an OpenCode plugin that lets you hand work to background agents while you keep using your main conversation. Ask a worker to review code, investigate a bug, or test a change. It works in a separate conversation and sends back a report with evidence.
You can open any worker to see what it did and send it a follow-up. For larger jobs, workflows run agents in parallel, pass results between steps, and keep a record so you can resume after a restart.
Threads 0.3.4 needs OpenCode 2.1 or later. For older versions, see compatibility.
-
Add the server plugin:
opencode plugin add @op1/threads
-
Restart OpenCode.
OpenCode loads the terminal UI from the server plugin automatically. You do not need a second entry in cli.json. See configuration for version pinning, limits, and the optional agent skill.
Ask your agent, replacing the path with an existing project folder:
Start a Threads worker in /path/to/my-app to review the auth changes.
Don't edit files. Report findings with file paths and evidence.
Your conversation stays free while the worker runs. The prompt footer shows its progress:
⠋ 1 worker ctrl+x j
Press ctrl+x j to open the Threads list. Select the worker, press Enter, and choose Open to read its conversation. You can also open the list with /activities.
The worker's report arrives in your main conversation. Ask your agent to send a follow-up if you need more detail. See Work with workers for roles, permissions, and stopping workers.
- Keep separate conversations for separate tasks. Each worker has a folder, an agent profile, and a model. You can inspect its work without mixing it into your main conversation.
- Get a verdict with evidence. Workers report
PASS,PASS WITH NOTES,FAIL, orINCONCLUSIVE. A worker that stops without a report has no verdict. Check the evidence before accepting the result. - See what needs attention. Threads opens no worker tabs by itself. The footer shows running work and requests for input. Workers that pass hide once idle; failed or unreported work stays visible in the list.
- Run work in parallel. Workflows coordinate multiple agents, pass results to later steps, and pause for your input. Their saved records let a resumed run reuse completed steps.
To start a workflow, describe the job with /workflow-run:
/workflow-run Review src/auth and src/billing in parallel. Confirm each finding independently.
Run /workflows to see the steps, open a worker, or pause, stop, and resume the run. See Run a dynamic workflow.
For a small lookup, OpenCode's built-in subagents may be enough. Use Threads when you want a conversation you can return to, or a workflow with several steps. Compare workers, workflows, and subagents.
- Work with workers: start, watch, follow up, and stop.
- Run a dynamic workflow: parallel work, checkpoints, and saved scripts.
- Configuration: compatibility, limits, commands, and shortcuts.
- Reference: tools, fields, and data shapes.
- How Threads works: permissions, retries, and recovery.
- Workflow heartbeats: monitor unattended workflows.
- Workflow runtime contract: write scripts by hand.
- Development: build, test, and release.
- Changelog: changes between versions.