Skip to content

fix(pstack): make the /poteto-mode chat the runner, poteto-agent a delegate only - #358

Open
dev2o wants to merge 1 commit into
cursor:mainfrom
dev2o:fix/pstack-poteto-mode-runner
Open

fix(pstack): make the /poteto-mode chat the runner, poteto-agent a delegate only#358
dev2o wants to merge 1 commit into
cursor:mainfrom
dev2o:fix/pstack-poteto-mode-runner

Conversation

@dev2o

@dev2o dev2o commented Sep 10, 2026

Copy link
Copy Markdown

Closes #357.

Why

On Cloud Agents only the main agent can spawn subagents. poteto-agent.md describes itself as the routing target for /poteto-mode. As a result, a Cloud Agent chat spawns one poteto-agent to run the entire playbook. That child agent has no Task tool and its todo_write calls fail. Investigation subagents, code delegates, Comment Sicko, and the todo list never run.

This change makes the receiving chat the runner everywhere. poteto-agent becomes a delegate wrapper for tasks spawned during a run.

Scope

  • pstack/agents/poteto-agent.md: update description and declare delegate role in the body.
  • pstack/skills/poteto-mode/SKILL.md: specify that the receiving chat runs the playbook and launches delegates.
  • pstack/skills/poteto-mode/playbooks/feature.md: clarify subagent spawning constraints on Cloud Agents.
  • pstack/README.md: reframe poteto-agent section to match the runner and delegate model.
  • pstack/.cursor-plugin/plugin.json: bump version from 0.15.1 to 0.15.2.

Blast Radius

Documentation and agent description changes only. No skill workflow logic changes. Workspaces that already run playbooks in the main chat experience no change. Workspaces running on Cloud Agents regain todo tracking and subagent fan-out.

Verification

  • Ran node scripts/validate-plugins.mjs. All plugins validated successfully.
  • Manual verification: /poteto-mode fix <bug> in a Cloud Agent opens the todo list in the receiving chat and launches investigator subagents from that chat.

Note

Low Risk
Documentation and agent metadata only; no runtime workflow logic changes.

Overview
Clarifies who runs /poteto-mode vs who poteto-agent is for, fixing Cloud Agent runs where a nested poteto-agent could not spawn subagents or maintain todos.

The chat that receives /poteto-mode is now documented as the runner (playbook, todo list, all Task spawns). poteto-agent is a delegate wrapper for code-writing and helper tasks spawned during that run, not a substitute for running the playbook. Updates land in poteto-agent.md, poteto-mode/SKILL.md, feature.md step 4 (IDE/CLI vs Cloud Agents spawning rules), and README.md. Plugin version bumps to 0.15.2.

Reviewed by Cursor Bugbot for commit 22c14fc. Bugbot is set up for automated code reviews on this repo. Configure here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pstack: poteto-agent description routes /poteto-mode into a nested runner, which loses Task and the todo list on Cloud Agents

1 participant