Skip to main content
A living document: updated as the project iterates. Priorities are open to discussion in issues.

Shipped

Desktop app

Multi-turn conversations, attachments, @-mentions, checkpoint rollback, prompt queueing, model picker, slash commands, voice input.

pi-agent sidecar runtime

MCP connectivity, skill loading, subagent scheduling, long-term memory, context compaction, built-in coding / browser / HTTP / screenshot tools.

Plugin system & office suite

The panel system and local marketplace, with office, canvas, and ui-design workspaces.

Credentials & system integration

Keychain-based credential management, webhook notifications, scheduled tasks, and appearance themes.

LAN remote access

Desktop gateway + pairing code + browser web client.

Mobile app

Expo + React Native over the same WebSocket gateway; QR pairing with tokens stored in the Keychain / Keystore.

In progress: the mobile app

The native shell has landed (Expo, not Tauri mobile — it reuses the desktop gateway’s /ws protocol and shares its origin with the web client). What remains is what mobile genuinely needs:
  • Push notifications — task complete, awaiting approval, scheduled task finished. This needs device-token registration and foreground keep-alive on the gateway side;
  • Biometric unlock + token rotation — tokens currently never expire, and revocation is limited to “revoke all devices” on the desktop;
  • Offline drafts and weak-network behaviour — queueing and in-flight stream resumption across cell/Wi-Fi switches;
  • Narrow-screen interaction polish — gestures, attachment picking, session list reflow.

In progress: strengthening remote access

Moving from “works on the same Wi-Fi” to “safe to use away from home”:
  • End-to-end encryption — negotiate keys at pairing time, encrypt WS traffic on the desktop so tunnels and relays see nothing in plaintext;
  • Stable public access — escape throwaway tunnel URLs, with fixed domains and automatic reconnection;
  • Disconnection and recovery — backfill messages missed during a WS outage, and reconcile session state after reconnect;
  • Concurrent devices — input arbitration and view sync across desktop plus multiple remotes online at once;
  • Remote approval — push dangerous-operation confirmations to paired devices and let them be approved from the phone.

Backlog

Release matrix

Code signing and auto-update for both macOS and Windows.

Performance

Cold-start latency and memory footprint in long sessions.

Plugin ecosystem

More official example plugins and third-party marketplace integration.

Session migration

User-facing entry points for moving sessions across devices and restoring backups.

Contributing

Nothing here is locked in — open an issue to discuss priorities. A useful issue carries the concrete scenario, how you work around it today, and the behaviour you expected.

License

Apache-2.0, and the notices you must keep.