Experimental Paseo provider for Pi. The root agent runs as a Pi RPC subprocess,
not through the in-process SDK. It depends on the plexus-pi Pi extension, which
owns tier/context controls, tree navigation, and reload through the
plexuspi-control command. The owned pi-subagents extension supplies the child
activity bridge. The plugin itself doesn't copy, install, or sync plexus-pi; the
isolated test launcher copies it for test runs only.
Tested with Paseo 0.11.0-beta.3, Pi 1.0.0+local, and DeepSeek
deepseek-v4.1-flash. SDK dependencies remain pinned to the common 0.12.0 API;
that pin is not a claim that newer hosts are unsupported.
- Model/thinking selection and service-tier choices discovered per model from
plexus-pi. Advertiseddefault,auto, andstandardtiers share onedefaultchoice in the composer; other names stay unchanged. Selection still sends an advertised tier to Plexus. Models without tier support have no service-tier selector. Catalog refreshes and model changes update it live. A context-length selector shows rounded budgets such as272Kand1Mon the button itself, with short/max choices. It appears only for models with distinct short/max budgets supplied byplexus-pi. Internally, Off uses the short budget and On uses the maximum; the UI shows token lengths, not On/Off. Models without a short budget retain Pi's declared limit and have no context selector. Settings → PlexusPi model names switches the picker between full names and the server-advertised short names (plexus-piv1.14.0+); models without an advertised short name keep their full name, whose picker line shows the full name alongside the id when short names are on. Settings apply to subsequent requests without interrupting a response. - Context usage and the effective budget are reported through provider usage
events (
get_session_statsconsumption plus the control-applied window). Consumption refreshes after assistant responses, with a two-second refetch backstop while a turn is active, including tool waits. After compaction, consumption stays unknown until Pi has a fresh measurement; it then recovers before the whole turn ends. Late snapshots cannot restore pre-compaction or closed-turn data. Backend errors are surfaced, not hidden behind an eligibility matrix. Legacy Fast selections migrate to advertisedpriority; unsupported saved tiers useautoorstandardwhile retaining the user's choice for compatible models. Premium-only lists remain unselected until the user chooses. Plexus handles upstream tier translation; PlexusPi sends the advertised spelling. - Private durable conversation handles and active-branch history restoration. Large histories are read from the owned Pi transcript instead of requesting one growing RPC response.
- Paseo's Fork action works as a text copy. The new session starts with the curated chat history plus your first message. Very long histories are truncated with a visible note; tool runs and child activity don't carry over.
- PlexusPi: Copy Pi resume command (stop session first) in the agent command center copies a terminal command for the saved native transcript. Stop/detach the Paseo session before running it to avoid concurrent transcript writers.
- Native
/compact,/reload,/autocompact,/model,/thinking,/name, and/sessioncommands are listed and dispatched without sending them to the model./reloadre-reads extensions, skills, prompts, themes, and context files (for example, skills that landed in the workspace after the session started) and republishes the command catalog; it runs only while idle and never touches the session history. Terminal-only built-ins fail explicitly; extension commands keep precedence. Run slash commands while idle: Paseo may interrupt an active turn before dispatching them./autocompactchanges Pi's global preference, not just this conversation; project overrides may still take precedence. - Active-turn steering through native Pi RPC, without interrupting tools or starting another turn. Steering accepts the same image/text/file inputs as ordinary prompts and honors requested pending-dialog cancellation. Idle steering and native/extension commands are refused; skills and prompt templates still expand in Pi. Stop clears queued steering before aborting. If a turn ends without consuming an accepted steer, PlexusPi discards it and reports a warning rather than carrying it into the next turn.
- Image/text/file inputs, native blocking dialogs, and an editor-prefill screen.
Open Pi dialogs from the command center (
Ctrl+Kon Linux). - Read-only native child views, ordered live activity, terminal outcomes, and an append-only child journal. Final activity is durable; streaming updates aren't repeatedly appended to the journal.
- Independent child defaults and model budgeting, nested bridge propagation, parent interruption that preserves background children, and root cleanup.
- Conversation rewind using OMP's navigation/configuration/replay sequence, adapted to Pi's public tree-navigation API. No file rollback or automatic resubmission.
This is not a declaration that every original V1 acceptance criterion passes.
Paseo's published 0.11 beta keeps an append-only provider history mirror. PlexusPi's rewind changes Pi's active branch correctly, but abandoned rows can remain in Paseo's visible history. Reloading an agent does not guarantee their removal. The limitation is covered by an executable host-contract test and verification notes.
Child journals retain activity beyond the host's cached-preview limits. A synthetic 520-row, multi-megabyte history reached row 259 in the native view; this does not establish every recovery/display path on every host version.
Arbitrary TUI widgets and MCP configuration/tool-policy translation are not
implemented. Nonempty MCP and exact preapproval requests
fail explicitly. Pi-managed retry defaults are left alone; /autocompact
controls automatic compaction and manual compaction is idle-only.
Daemon cleanup was tested on Linux. Windows descendant process-group cleanup is not implemented.
Registry costs are estimates, not verified billing. Context budgets come from Plexus policy metadata, not a separate backend probe. Text-only models receive a visible image-omission explanation rather than a claim that the image was analyzed.
Host API gaps, including the built-in resume menu and harmless child-outline errors, are tracked in PaseoShortcomings.md. The policy event contract and lifecycle are described in the Plexus context integration.
Install this plugin's dependencies:
npm --prefix plexuspi ciInstall the plexus-pi Pi extension in Pi as you normally would (see its README),
using a version that includes the plexuspi-control module. Pi loads it with its
other resources; PlexusPi doesn't take an extension path.
PLEXUSPI_PI_COMMAND optionally selects a Pi executable; the default is pi.
This is a daemon setting, not shell initialization performed by the plugin.
The daemon must inherit the intended PI_CODING_AGENT_DIR and PASEO_HOME.
They default to ~/.pi/agent and ~/.paseo. PlexusPi stores private manifests,
native transcripts, and child journals under
$PASEO_HOME/plugins/plexuspi/state. Pi subprocesses inherit the daemon
environment plus per-session overrides. Configure the host explicitly; Paseo
doesn't discover an arbitrary copied Pi installation. The isolated launcher in
testing writes that config and sets these paths for you.
Pi loads its normal resources, including plexus-pi. Known competing
tier/context owners cause a clear startup failure. Resolve that conflict in
your Pi configuration; PlexusPi does not disable extensions or rewrite defaults
for you. The current owned pi-subagents bridge changes are required for child
observation.
Use plugin CLI help before installation and reload:
paseo plugin install --help
paseo plugin install "$PWD/plexuspi"
paseo plugin reload --help
paseo plugin reload plexuspi
paseo plugin ls --help
paseo plugin ls plexuspi
paseo plugin logs --help
paseo plugin logs plexuspiSelect PlexusPi for a new Paseo conversation. Native-provider conversations aren't converted or imported.
Future work uses PlexusPi itself with this repository as the workspace. The provider label in Paseo remains PlexusPi.
- Read the docs index, then the current limits here and in Paseo shortcomings. The numbered research reports are source snapshots, not a list of unfinished implementation tasks.
- Run the checks below in both packages. Test changed runtime behavior in the isolated daemon, not the daemon hosting your work session.
- After
plexus-piedits, runnode plexuspi/testing/start.mjs --sync-resourcesand open a fresh test Pi session. After provider/client edits, reload PlexusPi on the isolated host. Check plugin load state/logs and the actual UI, not just CLI request success. - Before updating the active host, save changes and leave the next session a summary of changed files, checks, and unresolved limits. Run the active-host reload from a separate terminal. Plugin reload closes owned Pi processes, including the one running this development conversation.
Do not replace the root subprocess with Pi's in-process SDK, patch Paseo core, or add fixed model-policy fallbacks. Keep credentials in the daemon/Pi environment. To move a saved conversation into terminal Pi, use PlexusPi: Copy Pi resume command (stop session first) and stop/detach its Paseo session before executing the command. Supply required credentials/environment separately; never run two transcript writers at once. The copied command uses POSIX shell quoting.
npm --prefix plexuspi run lint
npm --prefix plexuspi run typecheck
npm --prefix plexuspi test
npm run sdk:checkplexus-pi lives outside this repository (in pi-stuff) and is checked in its
own package.
Client tests check bundle size, classes, server-boundary isolation, and Hermes bytecode compilation. The host-contract test uses an installed beta host only in tests, never as a production internal import.
For the isolated launch script and browser workflow, see testing. The original scope remains in requirements, with the architecture and staged acceptance goals and contract findings.
The rewind adaptation retains OMP's MIT notice in
THIRD-PARTY-NOTICES.