v0.3.0 — Sidekick for your existing workflow

Sidekick fits your existing workflow

Sidekick provides one persistent worker per invoking Pi session. Existing agent systems retain control of topology, scheduling, permissions, and workspace concurrency. Without another agent system, use the normal lead → Sidekick flow.

What's new since v0.2.0

• Select authenticated models from any Pi-registered provider, including custom providers; exact model/reasoning pinning remains enforced, with no automatic fallback.
• See elapsed task time and expand per-task activity, tool output, and reports with Ctrl+O.
• Compare recorded API-rate estimates in clearer cost cards, the current-branch footer, and /sidekick stats all. Saved-session totals deduplicate forked records and report incomplete data.
• Cancel any setup step without an error or changes to existing settings. Actual errors no longer get a duplicate Error: prefix.
• Use independent Sidekick sessions without package-imposed subagent topology or native Agent/Workflow launch restrictions. Sidekick's own trust checks, worker tool restrictions, and same-batch call protection remain.

Install

pi install git:github.com/7StaSH7/pi-sidekick@v0.3.0

Run /reload, then /sidekick setup if you need to change the worker model.

Validation and limitations

51 local offline tests passed, including session independence, cancellation, host-tool non-interference, and rejection of Sidekick work when the host reports an untrusted project. CI excludes the optional workstation-only footer test. No live-provider benchmark is claimed.

Cost comparisons are API-rate estimates for recorded Sidekick tokens, not guaranteed net savings or subscription billing; they exclude lead planning/review and other agent-system overhead. Session isolation is not a filesystem sandbox. Sidekick relies on the host's reported trust status and does not repair trust inheritance in other agent systems.

The attached pi-sidekick-0.3.0.tgz contains the package. No npm registry publication is part of this release.