opencode-autoplans

OpenCode plugin for autoplans.dev.

Install

Add to opencode.json (project) or ~/.config/opencode/opencode.json (global):

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["opencode-autoplans"],
  "mcp": {
    "autoplans": {
      "type": "remote",
      "url": "https://autoplans.dev/api/v1/mcp",
      "headers": { "Authorization": "Bearer {env:AUTOPLANS_API_KEY}" }
    }
  }
}

Then export your key:

export AUTOPLANS_API_KEY=apk_your_key_here

OpenCode installs the package with Bun at startup. To develop locally instead, drop this directory at .opencode/plugins/autoplans/.

Tools

| Tool | Purpose | | --- | --- | | autoplans_my_tasks | Tasks assigned to you, optionally filtered by status | | autoplans_list_projects | Projects with ids — call before any write | | autoplans_create_task | File a task on a project | | autoplans_update_task_status | Move a task between statuses | | autoplans_comment | Post a progress comment |

On session.created the plugin shows a toast if you have in-progress tasks.

The mcp block vs the plugin

They overlap on purpose. The mcp entry exposes all 28 autoplans tools generically; the plugin adds the five highest-traffic ones as first-class tools with tighter descriptions, plus the session toast. Keep both, or drop the mcp block if you only want the curated set.