Menú
Inspect and manage OpenCode sessions via the local HTTP API — list, check status, read history, create, and prompt sessions.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Read Slack threads or channel history and post concise bot replies through slack-post-message when the user asks to answer in Slack or when a Slack event payload provides channel and thread context.
GitHub CLI surface allowed by Thor's server-side gh policy. Append-only: Thor can create PRs, comments, and non-approval reviews but cannot approve, merge, edit, or delete prior artifacts.
Run project commands (build, test, lint) in a cloud sandbox with common runtimes and on-demand toolchains.
Query and analyze Langfuse observability data (observations, metrics, scores) via the mcp CLI for debugging LLM behavior, cost, and user activity.
Orchestrate real browser interaction, screenshots, recordings, and UI evidence without encoding app-specific flows.
Inspect LaunchDarkly feature flags, environments, segments, and metrics through the read-only ldcli wrapper.
Basado en la clasificación ocupacional SOC
| name | opencode |
| description | Inspect and manage OpenCode sessions via the local HTTP API — list, check status, read history, create, and prompt sessions. |
Use this skill when:
http://127.0.0.1:4096
All requests use curl. For repo-scoped requests, set the header x-opencode-directory: /workspace/repos/<repo>.
curl -s 'http://127.0.0.1:4096/session?directory=%2Fworkspace%2Frepos%2F<repo>'
Returns sessions sorted by most recently updated. Supports filters: directory, roots, start, search, limit.
curl -s 'http://127.0.0.1:4096/session/<sessionID>'
Returns session metadata including its directory — use this to resolve which repo a session belongs to.
curl -s -H 'x-opencode-directory: /workspace/repos/<repo>' \
'http://127.0.0.1:4096/session/status'
Returns a map of sessionID -> status. Idle sessions are omitted — {} means nothing is busy.
Important: always scope by repo. The global /session/status can return {} while a repo-scoped call shows busy sessions.
curl -s 'http://127.0.0.1:4096/session/<sessionID>/message?directory=%2Fworkspace%2Frepos%2F<repo>'
Returns conversation history including assistant internal steps and tool calls, not just user-visible replies.
If this returns 404, the session likely belongs to a different repo. Fetch the session first (GET /session/<id>), read its directory, and retry with the correct repo path.
curl -s -X POST -H 'content-type: application/json' \
-d '{}' 'http://127.0.0.1:4096/session'
The new session inherits the running OpenCode instance's directory.
curl -s -X POST -H 'content-type: application/json' \
-d '{"parts":[{"type":"text","text":"<prompt>"}]}' \
'http://127.0.0.1:4096/session/<sessionID>/message'
When asked about active or busy sessions:
GET /session/status with x-opencode-directory for each repo in scopeGET /session only for history/context, not active-status truthGET /session/<id> and GET /session/<id>/messageGET /session/<id> returns 404/workspace/worklog does not imply the session belongs to /workspace/repos/thor — sessions often ran in another repoPOST requests are not rewritten by the SDK's directory logic — only GET/HEAD are