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.
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.
Share with a team
Save wallet IDs with names, then put those contacts in a team:
Contact names, their public wallet keys, and team membership are defined in ~/.bitplan/config.json. A local draft may remember a team name so it can resolve the current members when you publish. Neither names nor membership go to the server or on-chain; only public wallet keys appear in the shared envelope. BitPlan has no accounts, membership database, or plan database.
Remove a member and the next version of a locally tracked plan will leave them out. Versions already shared with them cannot be revoked.
Browser agents
BitPlan's WebMCP tools can prepare a plan, list encrypted plan IDs, and open the viewer. They cannot publish or read decrypted plan text.