Claude Code
Session hooksRecall context during work and reflect after the session. Verify the installed hooks with your administrator before connecting confidential project material.
Bunshin / Documentation
Your agent.
Your company’s memory.
Connect the work you do to what your company knows. Start with your invitation, then give your agent a secure connection to the shared memory.
01Join your workspace
Open your company invitation and sign in with the invited email address. Your administrator assigns your role, team, and clearance. These determine which knowledge your agent can receive.
Sign in to Bunshin02Create an agent key
In your workspace, open Agent keys and create a key for this machine. Each key follows your account’s current permissions and can be revoked independently.
The full key is shown once. Save it securely and keep it out of source control and chat transcripts.
03Connect the pilot CLI
Your pilot administrator supplies the Bunshin package. With Node.js 20 or later installed, run:
Terminal
npm install -g ./bunshin-cli-0.1.0.tgz
bunshin initEnter the API address and profile shown alongside your agent key. Then follow the supported setup for your agent below.
Work with your preferred agent.
The pilot includes adapters for these harnesses. Your administrator will confirm the supported version and verify installation with you.
Codex
Pilot validationThe Codex adapter connects agent sessions to Bunshin. Installation and context delivery are being validated against the supported harness version.
Pi
Pilot validationThe Pi adapter brings company context into your agent’s work. Your administrator provides the setup and checks that lessons arrive as expected.
See what your company remembers.
Knowledge shows facts and workflows with their sources and visibility. Recall preview lets you see what an agent would retrieve for a task using your own permissions.
Conflicts surfaces knowledge that needs a human answer. Your administrator coordinates review with the lesson owners.
Open workspace