Use case · client projects
Freelancers often move between repositories and deadlines. Beeplane helps you find which local agent session belongs to each project before you review or reply.
This workflow assumes each client project is already available on your paired machine. Beeplane does not host client repositories; keep access controls and client data policies in your existing development environment.
Use your normal per-project directories and credentials. Do not paste client secrets into messages or share pairing access beyond your own trusted devices.
Before launching Claude Code, Codex CLI, or OpenCode, confirm the working directory and task scope for that client.
In Beeplane, use the project and session context to open the correct conversation. Read recent messages to avoid sending one client’s instructions into another task.
Inspect the diff and run that project’s checks on the host. Keep your normal client review and approval process before delivering work.
Repositories and credentials already separated on your own development machine.
Client data policies that prohibit using an AI agent or sharing project context with it.
Beeplane is designed around local session data; the relay passes encrypted requests and does not store transcripts. Keep your own machine and repository protections in place.
The session list includes project context to help identify work. Use the app’s current project/session controls for the available filtering behavior.
No. Repository permissions, secrets, and client data handling remain your responsibility on the host.
Free to download. Works with Claude Code, Codex, OpenCode, and other agents on macOS or Linux.