Skip to content
This repository was archived by the owner on Oct 15, 2026. It is now read-only.

Commit fdf5eb1

Browse files
committed
docs: confirm todo-tool removal from opencode V2 is permanent
github.com/anomalyco/opencode#42421 was closed by a maintainer as "Not planned" with the explicit statement "This is intentional in V2. The TODO tools are not currently planned." There is no todowrite/todoread tool anywhere in V2's built-in catalog, so the tool-hook-based reconstruction idea already footnoted here has nothing to observe for todo state specifically (file-touch reconstruction via edit/write hooks remains theoretically open, since those tools do still exist on V2).
1 parent 37cd590 commit fdf5eb1

1 file changed

Lines changed: 16 additions & 1 deletion

File tree

‎docs/v2-compat-audit.md‎

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,9 +53,24 @@ used for session-scoped file-edit attribution) and todo-state accumulation
5353
(`src/plugin.js:1471`, used for the latest-todo-list capture) are gone in
5454
any hypothetical V2 port, full stop.
5555

56+
**Update (2026-09-18): the todo half of this is now confirmed permanent,
57+
not merely absent from the tag we inspected.** GitHub issue
58+
[anomalyco/opencode#42421](https://github.com/anomalyco/opencode/issues/42421)
59+
was filed specifically against V2, and a maintainer replied directly:
60+
*"This is intentional in V2. The TODO tools are not currently planned."*
61+
The issue was closed as "Not planned." There is no `todowrite`/`todoread`
62+
tool anywhere in V2's built-in tool catalog (confirmed both by source
63+
inspection and the live V2 Tools docs), so there is nothing for a
64+
`ctx.tool.hook("execute.after")`-based reconstruction to observe — this
65+
option is not merely undesirable, it is impossible. Do not revisit the
66+
todo-signal drop expecting a future opencode release to reintroduce the
67+
underlying tool; treat it as permanent unless that upstream position
68+
changes.
69+
5670
> Footnote (not a plan): it is theoretically possible to reconstruct
5771
> file-touch data by hooking `ctx.tool.hook("execute.after")` on built-in
58-
> edit/write tool calls. This is explicitly **not** written up as a
72+
> edit/write tool calls — the `edit`/`write`/`patch` tools DO still exist
73+
> on V2, unlike the todo tool. This is explicitly **not** written up as a
5974
> committed workaround — see the "needs live verification" section below
6075
> for the one open question that would gate even considering it.
6176

0 commit comments

Comments
 (0)