Files
dots/common/.pi/agent/extensions/plan-mode/README.md
T
coja 1e39e0cb4b [Sync] replace the flat layout with the unified stow tree
Supersedes the old flat .config/ layout (last published 2026-06-28) with the
private repo's structure: one shared base plus per-host overlays.

- packages: common/ gui/ lw/ fl/ wm/ plus install.sh and bin/ tooling
  (dotsync, reconcile-hyde.sh)
- new README covering the layout, deploy order and the HyDE dependency
- current HyDE waybar rig (layouts/, cava), pi agent extensions, claude/
  config, tmux, presenterm, aichat roles
- fish: kp (keepassxc-cli + fzf picker, db path from $KP_DB) and
  bind_M_n_history (alt+1..9 recalls the nth history entry)
- drops cruft that should never have been tracked: the duplicate top-level
  .pi/ copy, btop.log, zellij config.kdl.bak, fish_variables
- .pi/agent/auth.json is gitignored; auth.json.example ships instead

Host-specific work sessions and the personal backlog stay in the private
tree. Endpoint locators in the llamacpp/whisper guides are placeholders
($SERVER, <own-domain>) — the guides themselves stay, since they are the
useful part.
2026-08-13 02:53:06 +02:00

2.0 KiB

Plan Mode Extension

Read-only exploration mode for safe code analysis.

Features

  • Built-in write tools disabled: Disables edit/write while preserving other active tools
  • Bash allowlist: Only read-only bash commands are allowed
  • Plan extraction: Extracts numbered steps from Plan: sections
  • Progress tracking: Widget shows completion status during execution
  • [DONE:n] markers: Explicit step completion tracking
  • Session persistence: State survives session resume

Commands

  • /plan - Toggle plan mode
  • /todos - Show current plan progress
  • Shift+Tab - Toggle plan mode (shortcut; this fork rebinds it from upstream's Ctrl+Alt+P)

Usage

  1. Enable plan mode with /plan or --plan flag
  2. Ask the agent to analyze code and create a plan
  3. The agent should output a numbered plan under a Plan: header:
Plan:
1. First step description
2. Second step description
3. Third step description
  1. Choose "Execute the plan" when prompted
  2. During execution, the agent marks steps complete with [DONE:n] tags
  3. Progress widget shows completion status

How It Works

Plan Mode (Read-Only)

  • Built-in edit/write tools disabled
  • Other active tools remain available
  • Bash commands filtered through allowlist
  • Agent creates a plan without making changes

Execution Mode

  • Full tool access restored
  • Agent executes steps in order
  • [DONE:n] markers track completion
  • Widget shows progress

Command Allowlist

Safe commands (allowed):

  • File inspection: cat, head, tail, less, more
  • Search: grep, find, rg, fd
  • Directory: ls, pwd, tree
  • Git read: git status, git log, git diff, git branch
  • Package info: npm list, npm outdated, yarn info
  • System info: uname, whoami, date, uptime

Blocked commands:

  • File modification: rm, mv, cp, mkdir, touch
  • Git write: git add, git commit, git push
  • Package install: npm install, yarn add, pip install
  • System: sudo, kill, reboot
  • Editors: vim, nano, code