Agents and wallets
A coding agent runs the BitPlan CLI. Your wallet keeps the keys and approves encryption and publishing.
Use BitPlan with a coding agent
Start and unlock a compatible BRC-100 wallet on the same computer. Then the agent can run:
The CLI never asks for a mnemonic or private key. The wallet still controls every permission.
Prefer a compatible wallet you already use. The 1Sat CLI is planned as a local fallback for agent sessions, but its current 1sat serve wallet command exposes wallet storage rather than the application-facing endpoint BitPlan needs. Do not configure it as a BitPlan wallet yet.
Read the same plan on your phone
If both devices use the same wallet identity, nothing else is needed. If they use different identities, add the phone wallet as a reader. BitPlan encrypts the plan for both wallets without copying either wallet's private keys.
- On the phone, open My drafts, connect the wallet, and choose Copy wallet ID.
- On the desktop, save that public ID as a default reader:
- Publish normally. New plans will include the phone wallet.
- Open the plan's viewer link on the phone.
The wallet ID is a public key, not a secret. Use npx bitplan config --clear-share-with to stop adding it to new plans.
Give the agent access
An agent with its own wallet gives you its public identity key. Follow Sharing and access to add it to a team and encrypt a new version for it. That guide also covers guest invitations and removing link access from future versions.
Browser agents
In an authorized, connected viewer, WebMCP tools can read the decrypted document with its annotations and per-author text edits, add a note, or save a live document edit. They do not sign or broadcast transactions. Tools belong to the outer viewer, not the untrusted plan iframe.
A browser agent can join an authorized live invitation and use the viewer. CLI fetch returns the saved document, not the room's annotations or live edits. Read those before proposing a revision. If a sandbox blocks wallet access or installation, request scoped permission or use the browser; do not work around its restrictions.
Turn feedback into a revision
Share and the revision sidebar use the same next-revision audience, saved for this plan in this browser. Only selected public keys enter a private-copy prompt, never your whole contact book. These choices do not change current access. A private copy does not revoke old links or make the existing live room wallet-only.
- Open New version. The publishing wallet chooses which suggestions to consider; other participants review their own contributions.
- Your authorized agent reads the live document and layers, then drafts changes.
- Copy the prompt. Publish on chain is off by default; turning it on requests an on-chain review, not automatic signing or payment.
Show live changes switches between the original loaded version and live edits and annotations. It does not discard shared work.
Replies belong to their own author and retain the parent's exact document target. Browser authorship is session-based, not yet verified wallet authorship. An on-chain layer must reference an on-chain plan revision; a hosted ID alone is insufficient. Author checkpoint signing, recovery and confirmed receipts are not yet connected end to end.
WebMCP is experimental and depends on browser support. Without it, use the authorized browser interface. A public plan ID in a prompt does not grant access.