Dispatch and collect long-running OpenCode sessions asynchronously via the HTTP API.
npx skills add https://github.com/corv89/hermes-stack --skill opencode-async-corv89
Please help me install this Agent Skill. Skill: opencode-async Source: https://github.com/corv89/hermes-stack/tree/main/skills/opencode-async Command: npx skills add https://github.com/corv89/hermes-stack --skill opencode-async-corv89
oc wrapper and upstream opencode2 CLI are blocking-only, so delegated coding tasks that run longer than the 600-second foreground terminal cap get silently truncated or misreported as failures. This Skill provides a fire-and-forget dispatch plus later collection pattern over the OpenCode server's HTTP API so long-running tasks complete server-side without losing output. ## Core Features & Use Cases - Async dispatch/collect scripts: oc_dispatch.py creates a session (or posts a follow-up turn), sends a prompt file, prints the session id, and exits immediately; oc_collect.py waits with permission auto-approval and SSE/polling, then prints the final reply. - Session-state diagnosis: Distinguishes healthy, done, and zombie sessions using finish, time.completed, pending permissions, and question endpoints, with a redispatch strategy for unrecoverable zombies. - Pitfall guidance: Documents pipe-truncation data loss, foreground timeout capping, exit-code-3 semantics, and provider fallback (zai-coding-plan vs exhausted main plans) via references/http-api.md. - Use Case: Delegate a 30-minute code review to the shared OpenCode server: dispatch the prompt file, capture the ses_... id, then collect the final review in a background terminal with completion notification. ## Quick Start Dispatch my task prompt file to the OpenCode server asynchronously and collect the session's final reply when it finishes.High-intent search queries and answers about installing and using this skill.
Dispatch the prompt with oc_dispatch.py, which creates a session via POST /api/session, sends the prompt, prints the session id, and exits immediately. Then run oc_collect.py with that session id in a background terminal to wait for and print the final reply.
No. Both the custom oc wrapper and the upstream opencode2 CLI are blocking-only; neither ships --dispatch, --wait, --status, or --collect flags. Async behavior must go through the server's HTTP API using the included dispatch and collect scripts.
Piping oc output through head, tail, or grep truncates the reply stream irreversibly; the text is only streamed, never stored server-side. Capture output with shell redirection to files in a background terminal instead of pipes.
Exit code 3 means the client-side wrapper timed out, but the server-side session is almost certainly still running and doing useful work. Do not report failure; reattach with oc --session <id> or collect the result with oc_collect.py.
A zombie session shows finish=None, null time.completed, no pending permissions or questions, and follow-up prompts add no messages. It is not recoverable; abandon it and dispatch a fresh session whose prompt bakes in everything the stalled session discovered.
Query GET /api/provider to list configured providers, then switch to a coding-plan variant such as zai-coding-plan, which often has separate billing from the exhausted main plan. Other fallbacks include bailian-personal, bailian-team, and the opencode Zen proxy.
gabesan21Invokes opencode CLI as a headless executor for delegated coding tasks with NDJSON output.
Dev10x-GuruGenerate fixup commits from JSON code review findings files.
SethyPagnaDelegate coding tasks to a multi-model Blackbox AI CLI agent.
234194027-cpuAutomate whitelisted Windows GUI applications via kc.exe with PowerShell.