Skip to content

todowrite tool not registered in v1.15.10 despite permission configuration #29118

Closed as not planned

Description

@sacrtap

Problem

The todowrite tool is listed as "environment-managed" in the system prompt but is NOT available in the tool list when running OpenCode v1.15.10 in TUI mode. This prevents the sidebar Todo panel from displaying tasks.

Environment

  • OpenCode version: 1.15.10
  • OS: Darwin 24.6.0 x64
  • Terminal: zed 1.3.6+stable / xterm-256color
  • Mode: TUI (confirmed)

Configuration

Global (~/.config/opencode/opencode.json)

"permission": {
  "todowrite": "allow",
  "read": "allow",
  "edit": "ask",
  "write": "ask",
  "bash": "allow"
}

Agent-specific (plan agent - default)

"plan": {
  "permission": {
    "bash": "allow",
    "edit": "ask",
    "write": "ask",
    "todowrite": "allow"
  }
}

Steps to Reproduce

  1. Install OpenCode v1.15.10: npm i -g [email protected]
  2. Configure "todowrite": "allow" in global or agent permissions
  3. Start OpenCode in TUI mode: opencode
  4. Try to use todowrite tool → Error: "Model tried to call unavailable tool 'todowrite'"

Expected Behavior

todowrite should be available as an environment-managed tool, and tasks created via it should appear in the sidebar Todo panel.

Actual Behavior

  • todowrite is NOT in the available tools list
  • Calling todowrite returns: invalid [tool=todowrite, error=Model tried to call unavailable tool 'todowrite']
  • Sidebar Todo panel does not show tasks

Additional Context

  • OhMyOpenCode (oh-my-openagent@latest) is installed and provides task_create/task_list/task_update tools, which work correctly
  • Tasks created via task_create are persisted to ~/.config/opencode/tasks/{project}/ but do NOT appear in the sidebar
  • Confirmed: OhMyOpenCode does NOT interfere with todowrite — searched native binary and source, no todowrite references found
  • SDK has Todo type and EventTodoUpdated event defined, suggesting the todo system exists but the tool is not registered

Plugins

- [email protected]
- @franlol/[email protected]
- @slkiser/[email protected]
- @mohak34/[email protected]
- [email protected]
- [email protected]
- [email protected]
- plugins/rtk.ts
- plugins/openviking-memory.ts
- @tarquinen/opencode-dcp@^3.1.12
- oh-my-openagent@latest

Workaround

Use task_list to view tasks (OhMyOpenCode), but sidebar Todo panel remains non-functional.

Activity

  1. github-actions commented on May 24, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    If your issue is distinct (e.g. specific to TUI mode or v1.15.10 regression), please add that context and reference the above issues so maintainers can link them.

  2. fadedlamp42 commented on May 25, 2026

    @fadedlamp42

    For anyone who cares, I spun up a low-effort fork to restore it: https://github.com/fadedlamp42/fadedcode

    Just run bun install, ./build.sh I added, then write an opencode script somewhere in your PATH like this (replacing "clone path" and possibly darwin):

    #!/bin/bash
    OPENCODE_DISABLE_CHANNEL_DB=true <clone path>/fadedcode/packages/opencode/dist/opencode-darwin-arm64/bin/opencode $@

    ...and it's a drop-in replacement.

  3. sacrtap commented on May 25, 2026

    @sacrtap
    Author

    For anyone who cares, I spun up a low-effort fork to restore it: https://github.com/fadedlamp42/fadedcode

    Just run bun install, ./build.sh I added, then write an opencode script somewhere in your PATH like this (replacing "clone path" and possibly darwin):

    #!/bin/bash
    OPENCODE_DISABLE_CHANNEL_DB=true /fadedcode/packages/opencode/dist/opencode-darwin-arm64/bin/opencode $@
    ...and it's a drop-in replacement.

    Is there a plan to merge branches and publish them?

  4. fadedlamp42 commented on May 25, 2026

    @fadedlamp42

    Is there a plan to merge branches and publish them?

    If your question is "will you ever pull from upstream?", the answer is "yes, occasionally when I notice a missing feature/performance degradation that's solved by upstream". If the question is "will you take steps to get this into package managers like brew", not unless people actually use it.

    I'd certainly respond to PRs and issues if they relate directly to divergences on the fork itself, but this is more of a "I disagree with one decision opencode made" than a "I passionately want to develop my own, independent agent harness".

  5. github-actions commented on Jul 24, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions