Tags
v0.5.3 — in-window subagent activity panel (live tool calls + reasoning snippets)
Artifacts
v0.5.2 — live subagent progress in the status bar + RND_DIR moved to the PI agent dir
Artifacts
v0.5.1 — fix /rnd-audit: dedicated rnd-auditor agent replaces the mis-targeted rnd-polisher spawn
Artifacts
v0.5.0 — Effect.ts substrate + real fix for the recurring anthropic fallback (stale global agents shadowing bundled no-model agents)
Artifacts
v0.4.3 — Fix subagent provider inheritance via ctx.model session-context cache.
Artifacts
v0.4.2 — surface subagent error detail in spawn-failure notify messages
Artifacts
v0.4.1 — Hotfix: runtime portability
- /rnd-doctor round-trip now probes rnd-cleanup (a real bundled agent) instead of Explore (Claude Code built-in with no PI equivalent).
- All 11 bundled agent .md files have model: removed; agents inherit the PI session model (cliproxy / direct provider / whatever the user trusts).
- session_start hook resolves rndDir via computeRndDir(process.cwd()) instead of the Claude-only RND_DIR env var.
See CHANGELOG.md.
Artifacts
v0.4.0 — Full Claude rnd-framework parity port
10 milestones shipped (M1-M10). Major surface expansions over v0.3.0:
- 4 → 11 subagents
- 11 → 35 methodology skills
- 2 → 13 slash commands
- 3 → 6 PreToolUse gates
- 0 → 4 lifecycle hook subscriptions
- 0 → 7 registered CLI flags
Runtime pipeline now: plan → discover → design → build → audit → verify → iterate → cleanup → polish → integrate. Verdict-map routing replaces v0.3's coarse pass/fail. Wave-level iteration with criticality budgets. Multi-judge consensus + tiebreaker for HIGH-criticality waves. Amendment flow with --rnd-amend flag. Calibration log accrues per-task verdicts.
See CHANGELOG.md for the full deliverables list.
Artifacts
v0.3.0 — Native subagents
Replaces the @tintinweb/pi-subagents peer dependency with an in-tree
subagent module built on PI's public createAgentSession SDK.
Behavior:
- RPC contract preserved bit-for-bit (subagents:rpc:{ping,spawn,stop}
with the same reply envelope; subagents:{created,started,completed,
failed} lifecycle events). Existing call sites in
src/orchestrator/spawn.ts and src/doctor.ts are unchanged.
- New module: src/subagents/{agent-defs,manager,rpc}.ts (~390 LOC).
- /rnd-doctor bumped to v0.3 with native-module messaging.
Breaking:
- @tintinweb/pi-subagents removed from peerDependencies.
- Steered-event and /agents-command surfaces from the original
protocol are not emitted/registered (they were unused by pi-rnd).
Manual verification before publishing:
pi -e ./src/index.ts
/rnd-doctor
Expect: 'pi-rnd — doctor v0.3' header and round-trip OK against
the configured LLM provider.
Artifacts
pi-rnd v0.2.8
Self-installing agents. pi-rnd now auto-copies its bundled agent .md files into ~/.pi/agent/agents/ at extension load time (only if not already present — never overwrites user customizations). This fixes the v0.2.7 hole where /rnd-doctor reported ✓ on bundled-path agents but /rnd-start failed because pi-subagents' loadCustomAgents only reads .pi/agents/ and ~/.pi/agent/agents/.
The doctor's discovery check no longer probes the bundled package path — that path was misleading because pi-subagents never reads from there. After v0.2.8 the agents are always at ~/.pi/agent/agents/ on second pi startup (first startup auto-installs).
Long-term fix is upstream: pi-subagents (or pi-coding-agent) should support a 'pi.agents' package manifest field for npm-published agent definitions, mirroring how 'pi.skills' already auto-discovers from npm packages. Not pi-rnd's call to make.
Artifacts
pi-rnd v0.2.7
When the subagent starts (subagents:started fires) but the LLM call doesn't complete in time, the doctor now reports the round-trip as a warning (⚠) rather than an error (✗). The agent system is working; only the user's LLM/proxy is slow — pi-rnd's own functionality is unaffected. Shortened timeout from 90s to 30s since the 90s test showed the call genuinely doesn't return — longer waits just delay the inevitable.
The 'never transitioned to running' case still returns error since that indicates a real pi-subagents internal problem.
Artifacts
pi-rnd v0.2.6
Fix the doctor's lifecycle observability for real this time. The previous fix moved the listener registration before the spawn RPC but kept gating on targetId !== null. Because the entire RPC spawn flow (emit → manager.spawn → startAgent → onStart → subagents:started) runs synchronously on the same JavaScript tick, subagents:started fires BEFORE we have targetId — listener skipped silently.
Real fix: buffer all started events into a Map<id, ts> in the listener with no gating. After spawn returns and we know targetId, look up the Map. This separates 'never started' from 'started but slow' correctly even when the started event arrived during the spawn RPC call itself.
Artifacts
pi-rnd v0.2.5
Doctor probe now passes 'claude-haiku-4-5-20251001' (no provider prefix) instead of 'anthropic/claude-haiku-4-5-20251001'. resolveModel falls through to fuzzy matching when there's no slash, picking up whichever provider hosts the model id — works for cliproxy, anthropic, or any other proxy/host.
Artifacts
pi-rnd v0.2.4
Change /rnd-doctor round-trip probe to use the Explore default agent with model: 'anthropic/claude-haiku-4-5-20251001' instead of general-purpose with no model override. Diagnoses whether the v0.2.2/v0.2.3 hang was caused by general-purpose's reliance on a possibly-unset session default model. Explore is read-only and fast (≤5s typical). If this still hangs we know the issue is broader than model resolution.
Artifacts
pi-rnd v0.2.3
Fix: /rnd-doctor round-trip probe now sets bypassQueue: true in its spawn options. Without it, the doctor's general-purpose probe gets queued behind existing background agents (maxConcurrent default = 4) and stays queued indefinitely if no other agent completes. The doctor probe is a one-shot test; bypassing the queue is correct.
Source reference: @tintinweb/pi-subagents agent-manager.ts:135 — queueing logic; schedule.ts uses bypassQueue:true for the same reason.
Artifacts
pi-rnd v0.2.2
- Fix race in /rnd-doctor round-trip lifecycle listener (was registered after spawn RPC, missing subagents:started)
- Drop bogus subagents:created listener (not emitted on RPC spawn path per pi-subagents source)
- Improved diagnostic: distinguish 'agent never transitioned to running' from 'agent started but LLM hangs'
- Drop max_turns from 3 to 1 for the round-trip probe (single LLM call, faster predictable test)
- Add project CLAUDE.md with session learnings
Artifacts
pi-rnd v0.2.1 — first npm release (v0.2.0 failed CI version-check, no force-push)
Artifacts
pi-rnd v0.2.0 — methodology-first port of rnd-framework to PI runtime
Ships:
- 11 methodology skills (using-rnd-framework, rnd-{orchestration,decomposition,scaling,iteration,building,verification,experiments,failure-modes}, kiss-practices, fp-practices)
- 4 subagent definitions (rnd-planner, rnd-builder, rnd-verifier, rnd-integrator)
- /rnd-start <task> orchestrator (plan -> build -> verify -> integrate)
- /rnd-doctor v0.2 (PI runtime + agent/skill discovery + gate registry + round-trip)
- Composable tool_call gate registry with 3 seed gates