Files
pi-ask/docs
jb 80da307828
CI / validate (push) Failing after 13s
feat: support ask flow in RPC clients
2026-08-22 21:55:08 -04:00
..
2026-05-04 00:03:13 +02:00
2026-06-22 01:10:11 +02:00

Docs

This folder keeps only the documentation needed to understand and maintain the extension without turning docs into a second copy of the code.

Files

  • configuration.md — source of truth for configuring pi-ask keymaps, behaviour, and /answer extraction
  • contract.md — external behavior, tool payload/result details, and UX guarantees
  • remote-events.md — local inter-extension event contract, bridge examples, and smoke-test steps
  • architecture.md — module boundaries and invariants
  • ../skills/ask-user/SKILL.md — auto-bundled agent-side decision-gate guidance; enabled by default, but can be disabled via pi config; inspired by https://github.com/edlsh/pi-ask-user

Reading order

  • start with configuration.md for config-editing rules
  • read contract.md for behavior
  • read remote-events.md for local bridge/event integration
  • read architecture.md for code layout

Local test run

From repo root, run:

pnpm dev
pnpm dev ../some-target-folder

This starts pi in isolated mode, loads only this extension and bundled ask-user skill, and uses the optional folder as --cd target.

Rule of thumb

If a detail is about implementation mechanics, it should usually live in src/ or tests/, not here.