Codex-style long-running goal mode for OpenCode.
This plugin adds:
/goal <objective>as an OpenCode command for TUI, desktop, and web.- A sidebar goal indicator with status, elapsed time, and objective.
- Agent tools:
get_goal,create_goal,set_goal,update_goal, andclear_goal. - Goal close evidence:
completerequires verified evidence, andunmetrequires a concrete blocker. - Persistent per-session goal state.
- Optional automatic continuation on
session.idle. - Compaction context so active goals are preserved when OpenCode summarizes a long session.
Install locally for the current OpenCode project:
opencode plugin @prevalentware/opencode-goal-pluginInstall globally:
opencode plugin -g @prevalentware/opencode-goal-pluginOpenCode detects both package entrypoints and writes the plugin into the server and TUI config targets.
If you configure it manually, add the package to both config files.
opencode.json:
{
"plugin": ["@prevalentware/opencode-goal-plugin"]
}tui.json:
{
"plugin": ["@prevalentware/opencode-goal-plugin"]
}Server options can be configured in opencode.json:
{
"plugin": [
[
"@prevalentware/opencode-goal-plugin",
{
"auto_continue": true,
"max_auto_turns": 25,
"min_continue_interval_seconds": 3
}
]
]
}Defaults:
auto_continue:truemax_auto_turns:25min_continue_interval_seconds:3register_command:truecommand_name:"goal"
Use /goal <objective> in a fresh OpenCode chat to create a long-running goal:
/goal review the frontend and translate visible English UI text to Spanish
Bare /goal reports the current goal state. /goal clear clears the goal. The TUI also includes a Goal command-palette entry for viewing, refreshing, or clearing the current goal state without creating a new goal.
You can also ask the agent to formulate the objective and call set_goal itself, for example: "set your own goal to finish this refactor safely." The tool uses the agent-written objective but still only creates a goal when explicitly requested.
When writing the objective, include the scope, non-goals, and verification path when they matter. The agent is reminded to audit real files, command output, tests, or PR state before closing the goal.
The update_goal tool can close a goal in two ways:
status: "complete"withevidencewhen every requirement is actually achieved.status: "unmet"withblockerwhen the objective cannot be achieved or is blocked by missing external input.
Goal state is stored at:
$XDG_DATA_HOME/opencode-goal-plugin/goals.json
If XDG_DATA_HOME is not set, the default is:
~/.local/share/opencode-goal-plugin/goals.json
Set OPENCODE_GOAL_STATE_PATH to use a custom file.
bun install
bun test
bun run lint
bun run typecheck
bun run build
npm pack --dry-runThis package is set up for npm Trusted Publishing from GitHub Actions. On every push to main, CI runs typecheck, lint, and unit tests in parallel. If they all pass, the publish job computes the next patch version from the latest version on npm, builds the package, and runs npm publish.
Before the first automated publish, configure the package on npm:
- Open the package settings on npmjs.com.
- Add a Trusted Publisher for GitHub Actions.
- Use repository
prevalentWare/opencode-goal-plugin. - Use workflow file
publish.yml.
The repository must be public for npm provenance to be generated automatically.
OpenCode plugin modules are target-specific. This package exports separate modules for server hooks/tools and TUI UI:
{
"exports": {
"./server": "./dist/server.js",
"./tui": "./src/tui.tsx"
}
}Codex goal mode has deeper runtime integration for thread lifecycle control. This plugin implements the same workflow using OpenCode plugin hooks. Token usage is read from OpenCode step-finish usage when available and falls back to message token metadata or text estimation when exact usage is unavailable. Continuation is driven by OpenCode's session.idle event.