Skip to content

Latest commit

 

History

History
26 lines (16 loc) · 2.98 KB

COMPATIBILITY.md

File metadata and controls

26 lines (16 loc) · 2.98 KB

Qoder compatibility

pstack 0.15.42 runs on Qoder. The core poteto-mode workflow is compatible. This file records what is verified, what needs setup, and what is out of scope.

Verified compatible

  • The manifest .qoder-plugin/plugin.json and marketplace.json use the Qoder plugin format.
  • Both agents, poteto-agent and comment-sicko, register and appear in the Agent tool list.
  • The plugin ships 61 skills. Four are model-invocable: control-cli, control-ui, deslop, and setup-pstack. The other 57 set disable-model-invocation: true, so Qoder hides them from model invocation but keeps them slash-invocable and file-routable.
  • The skills use Qoder tool names such as Agent, TaskCreate, and Skill. No Cursor tool name or cursor-agent CLI reference remains.
  • The default models Fast and Ultimate are valid names in qodercli --list-models. Code, prose, and judgment default to Ultimate xhigh. The hardest tasks default to Ultimate max. Reflect tooling and swarm workers default to Ultimate high. Review panels default to Ultimate high and Fast high.
  • Every subagent_type reference points to a registered agent.

Bugbot detection

skills/poteto-mode/scripts/watch-pr/github.ts detects bugbot comments without a host-specific account or marker. isBugbot returns true when the author login contains bugbot, or when the body carries a bot marker: automation_id, run_id, agentic security review, or bugbot. passKey reads RUN_ID: and AUTOMATION_ID: with any prefix, so CURSOR_AUTOMATION_ID: and QODER_AUTOMATION_ID: both parse.

Qoder's exact bugbot login and marker are unverified. Detection covers any host whose bot login contains bugbot or whose comments carry these markers. A host that uses a different marker needs a new entry in the isBugbot body-token list and the passKey regex list.

Model setup

Run /setup-pstack to write ~/.qoder/rules/pstack-models.md and the model-pinning profiles under ~/.qoder/agents/. The rule carries a # defaults: 2 line. A rule without that line is from an older setup. On the next run, old default values take the new defaults: a Fast value at any effort in feature, refactoring, bug-fix, perf-issue, hillclimb, reflect tooling, or swarm workers; an Ultimate value in hardest tasks; and a panel list that is exactly one Ultimate entry and one Fast entry. Every other value stays as the user's choice. A line whose role is not in the current shape, including the retired roles how explorer, how explainer, why investigators, and why synthesizer, is dropped. Until you run setup, roles use the documented auto fallback: Explore for read-only work and poteto-agent for write work. The fallback works. The pinned-model path stays inactive until setup runs.

Out of scope

The benny Slack automations are not a compatibility target. Qoder has no surface that creates a Slack-triggered automation, so the pack stays dormant and unsupported. automations/benny/FOR_AGENTS.md records this limit.