Opencode Lane

opencode-lane

Info (print and stop)

If $ARGUMENTS is info, or the user says info / справка / как запускать this skill: print the block below verbatim (Russian), then stop. Do not edit the plugin.

opencode-lane — OpenCode-половина Claude Lane

Роли
- Claude Code = PM: run-init, run-supervisor, lane-ctl owns/verify/accept.
- OpenCode = писатели (Grok и любой другой model через lane-session).
- Этот плагин = единственное НАШЕ нововведение внутри OpenCode-сессии.

Куда класть код
- Вход: profiles/opencode/opencode-lane.ts (только re-export).
- Код:  profiles/opencode/opencode-lane/<mod>.ts + проводка в index.ts.
- Живое: ~/.config/opencode/plugins/opencode-lane.ts + plugins/opencode-lane/.
- Не второй plugin-файл. Не новое имя в opencode.json.

Конвейер
- lane-session без --pure (плагин должен грузиться).
- Env: LANE_TASK_FILE, LANE_PROMPT_FILE, LANE_STACK_ROOT, TYPESAFE_API_KEY.
- Выкл Jev extra: LANE_OPENCODE_JEV=0. Выкл effort: LANE_JEV_EFFORT=0.
- Fail-open: Jev/winnow упал → сессия как без плагина, строка в jsonl.

Нельзя
- owns / verify / accept / retry — не сюда (lane-ctl, lane-session).
- Глотать чужие плагины (agentmemory-capture, gemini-auth, open-cursor).
- Второй планировщик на Jev. Jev = System One, не coding LLM.

Как открыть шпаргалку
- Claude Code: /lane-stack:opencode-lane info
- OpenCode TUI: /opencode-lane  (файл ~/.config/opencode/commands/opencode-lane.md)
- Не /lane-stack:… в палитре OpenCode — это namespace Claude-плагина, там его нет.

Диагноз прогона
- Сказать «делай диагноз».
- Лог: сосед LANE_PROMPT_FILE → opencode-lane.jsonl
  при read-only .agents → ~/.config/opencode/opencode-lane.jsonl
- Запуск/инструменты/stderr: provider.events.jsonl рядом с provider.out.
- Связь: task + session + call/message ID; log_origin указывает попытку.

Canonical files: profiles/opencode/opencode-lane.ts, profiles/opencode/opencode-lane/index.ts, bin/lane-session (attach_lane_contract_env, opencode argv). Skills lane-contract (YAML) and orchestrator-lanes (DAG) stay separate.

Load typesafe-ai when adding a Jev question. Keep known rules in code; Jev only supplies a typed judgment.

Split (do not blur)

A judgment that changes accept/retry/merge belongs in lane-ctl, not here. The plugin may only append a [opencode-lane …] note and a jsonl row. The writer still decides; the controller still gates.

Add an OpenCode change

1. One module under profiles/opencode/opencode-lane/. One hook concern.
2. Wire it in index.ts. Re-export from opencode-lane.ts only if tests or agents import the symbol.
3. Fail-open: catch, laneLog({ mod, ok: false, err }), keep the session.
4. Brand every user-visible string [opencode-lane <mod>].
5. install.sh already copies opencode-lane.ts + the folder. Do not add a second plugin list entry.
6. Copy live: ~/.config/opencode/plugins/opencode-lane.ts and plugins/opencode-lane/*.ts. A checkout-only fix is not shipped.
7. One smallest test in tests/test_jev_route.py (string wire or a node --experimental-strip-types check). No extra harness.

OpenCode hooks this plugin uses:

• chat.message — remember prompt, skill-hint
• chat.params — Jev effort
• tool.execute.before — block write over an existing file and git checkout/restore/reset/switch
• tool.execute.after — winnow, diagnose
• All tool events, including glob/MCP/edit/write/errors, feed progress diagnostics; Winnow still filters only read/grep/bash/shell. Novel output is evidence to inspect, not proof of task completion. first_edit_callback_ms measures a callback, not a verified file change.
• experimental.chat.messages.transform — evidence, sticky; no extra history compaction

If OpenCode grows a new hook, handle it in index.ts, not a sibling plugin.

Diagnose a writer run

User said «делай диагноз» — do this, then stop unless they said «чини».

1. Read the jsonl (newest last):

f="${LANE_PROMPT_FILE%/*}/opencode-lane.jsonl"
[ -f "$f" ] || f="$HOME/.config/opencode/opencode-lane.jsonl"
tail -n 40 "$f"

2. Filter by task, session, and log_origin (the fallback is shared). Classify rows by mod: startup telemetry jev route winnow sticky diagnose skill-hint evidence budget. ok: false is an error or retry. telemetry records session errors, assistant errors, tool running/completed/error, permission events, and lifecycle events. budget rows with dup: true are repeated results. On the third identical read/grep result, repeated_read emits a deterministic hint to reuse the result or report a blocker. It does not terminate the writer or change controller retry/acceptance policy.
3. Confirm the conveyor actually loaded us:
   • argv has no --pure
   • ~/.config/opencode/opencode.json plugin contains ./plugins/opencode-lane.ts
   • LANE_TASK_FILE was in the process env (sticky empty without it)
4. Report: module, last err, whether the session continued (fail-open). Do not patch until asked.

Provider and startup diagnostics

lane-session launches OpenCode with --print-logs --log-level WARN and writes provider.events.jsonl next to provider.out. This works even if the plugin never loads. It includes startup stderr, protocol errors, tool status/call/message IDs, input/output hashes, safe path/offset fields, step boundaries, and the final process result. provider.out retains the writer text; prompt.md is the exact dispatch prompt. Cursor ACP warnings/errors are forwarded to the same stderr journal via CURSOR_ACP_LOG_CONSOLE=1 and CURSOR_ACP_LOG_LEVEL=warn, because its default ~/.opencode-cursor file logger is outside the sandbox's writable mounts.

Lane writers set OPENCODE_CONFIG_CONTENT={"snapshot":false,"compaction":{"auto":false,"prune":false}}. Parallel writers in the same checkout otherwise race on OpenCode's shared snapshot Git index; stale root-owned snapshot objects can also reject writes. This disables OpenCode UI undo for lane writers only. Lane's own change tracking, owns/verify/accept gates, and interactive OpenCode config stay intact. See https://opencode.ai/docs/config/#snapshot.

Jev failure diagnosis requires a nonzero integer metadata.exit from the tool result. Successful reads/grep and results without an exit code are not failure evidence, even if their text contains error or failed. The existing failure-text gate still applies; known credentials are redacted from the task/output excerpt before it is sent to Jev. Actual tool errors remain in event telemetry regardless of Jev diagnosis.

The plugin uses OpenCode's documented event hook and mirrors its errors through client.app.log(). Native logs live under ~/.local/share/opencode/log/. Find full tool arguments/results by session and call ID in OpenCode's session store (opencode export <sessionID>). Telemetry intentionally excludes full file contents, reasoning, and shell arguments; known credential patterns and environment secret values are redacted.

Plugin journals rotate at 5 MiB; provider journals at 1 MiB; each keeps one backup (.1). Missing startup records can mean an old process, disabled logging, a load failure, or an unwritable log destination. Check stderr and the native log before assuming that a missing journal means no errors. A heartbeat proves process activity, not progress or successful acceptance.

Sources: https://opencode.ai/docs/plugins/#events, https://opencode.ai/docs/plugins/#logging, https://opencode.ai/docs/troubleshooting/#logs.