You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Submission] opencode-temporal — Temporal tools for the OpenCode coding agent #152
Temporal tools for the OpenCode coding agent: list and describe schedules and workflow executions, pause/unpause/trigger schedules. Authenticates with temporal cloud login OAuth — no static API keys in any config.
Long Description
opencode-temporal is an OpenCode plugin that registers a temporal tool namespace (7 tools) backed by the official temporal CLI. It is published on npm (opencode-temporal) and installs with opencode plugin add opencode-temporal.
What makes it different from existing Temporal MCP servers: there are no static API keys anywhere. Every call runs through the official CLI, which authenticates with the OAuth login stored by temporal cloud login (browser sign-in; the CLI mints, uses and refreshes short-lived tokens itself). Access is therefore scoped to the logged-in identity's RBAC role and is fully revocable by deactivating that user — no long-lived shared credentials on the agent host.
Tools:
list_schedules / describe_schedule — schedules with specs, pause state, notes, next action times (JSON)
list_workflows / describe_workflow — workflow executions by visibility query (JSON)
pause_schedule / unpause_schedule / trigger_schedule — schedule lifecycle, routed through OpenCode's permission system so hosts can require confirmation per schedule (useful when lanes trigger paid work)
Designed for ops use cases like ours: a coding agent that can safely inspect and operate production Temporal schedules (freshness-driven onepager regeneration across ~3.9k entities) without holding a permanent credential. Works with any Temporal Cloud namespace; self-hosted works via mTLS options through the same CLI.
Activity