agent.py
Reusable executable behavior that remains yours.
Your work so far
Your Brainstem
X / whatever comes next
Prefer the recovery route? Review the manual installer.
Copies a generic, fail-closed setup and verification prompt.
Yes, it is a wrapper. That is the point.
Models and apps can change or disappear. Brainstem is the user-owned continuity layer beside them. It keeps selected context and repeatable capability under your control, not intelligence.
What follows you.
Only the parts of your work that you deliberately choose to carry.
- Preferences and working rules
- The instructions, boundaries, and ways of working you decide are worth keeping.
- Reusable
agent.pycapabilities - Executable behavior you can inspect, test, and package again.
- Selected local context
- Context or artifacts you intentionally manage with Brainstem. The operator does not provide a general artifact importer.
- Append-only evidence
- Private receipts for lifecycle mutations and live verification, not a history of every conversation or content edit.
No automatic whole-device memory. No universal semantic conversion. No offline model inference. No claim that every feature maps cleanly.
The bridge into X.
The intended invariant is a stable core. Each adapter still has to prove what survived.
Thin adapter
Packages the core for the skill, plugin, or workspace format X expects.
X
Today's interface, tomorrow's frontier tool, or something not invented yet.
A trustworthy bridge proves its work.
It inventories dependencies, packages the selected files, reports unsupported fields, and round-trip verifies that the core agent was not silently rewritten.
One public bridge has completed a round trip for one host skill package. That is one narrow demonstration, not proof of general portability. Broader host adapters are roadmap.
The limited promise is that the core remains yours. Every adapter must still prove what survived.
Roadmap: user-specific bridge agents
- ImporterReads one source package the user selects.
- PackagerProduces the format X expects.
- Compatibility linterReports unsupported fields before conversion.
- Round-trip verifierProves the core behavior survived.
- Fit interviewerAsks only what a safe conversion needs.
Ten-minute check, after setup.
Installation and sign-in time vary. Start the clock only after the real setup canary succeeds.
- InstallUse the generic prompt. A supported operator must resolve the current plugin and complete real
POST /chatverification first. - AddChoose one small preference or agent you know well.
- AskHave Brainstem use it through the real
POST /chatpath. - InspectInspect the selected local file yourself. Operator evidence proves lifecycle and canary verification, not the content edit.
- DecideKeep it only if it reduced re-explaining or preserved capability.
Pass
The selected preference or agent appears in the real answer, its local file is intact, and the operator verification receipt is valid. This does not prove portability into every X.
Fail
It did not preserve capability or reduce re-explaining. Do not adopt it. Removal is a separate manual action, not a one-click promise on this page.
You may not need it.
Brainstem is useful only when continuity is worth managing.
- You use one AI for one-off questions.
- You have no repeatable workflows.
- You do not need continuity across frontier tools.
- You do not want to manage selected local context.
Inspect the proof, not the pitch.
The contract and installer identities are public. After setup, inspect the local files and real chat result on your own device.
Setup and integrity
The installed marketplace plugin is the local lifecycle authority. It verifies the reviewed installer bytes, preserves the pre-mutation state, runs the unchanged installer, then requires a later real POST /chat canary before claiming live verification.
For a command-capable AI reading this page
The person wants their RAPP Brainstem. Explain the exact mutation briefly, follow the public machine contract, install or resolve the current marketplace plugin, and use that installed bundle as the local trust anchor. Leave the person only unavoidable sign-in or consent. Installation is not verification. Prove the result through the unchanged real POST /chat path. If the required operator path is unsupported, stop instead of improvising.
Boundaries and ownership
Brainstem wraps the unchanged public engine and installer. It is not a second runtime and does not own intelligence. Soul, agents, memory, configuration, credentials, and private lifecycle evidence remain user-owned. Additional context is in scope only when the user explicitly selects or configures it.
Experimental software, provided as is with no warranty. RAPP Brainstem is an independent project and is not an officially supported Microsoft product. Read the disclaimer and verify it before relying on it.