Your projects. A working relationship.
One Bot for each project. Give it a goal, let it coordinate the work, and return for the decisions that need you. Execution, permissions and evidence stay under local control.
The project Bot experience is in the 0.1 preview. The 0.0 stable release uses the classic interface.
Start with something real
Code, documents and research can share the same working relationship. Start with a goal and a boundary; keep the relevant project close.
“Find why this request is slow, and fix the cause.”
The Bot reads the project, narrows the scope and delegates bounded changes with criteria for checking the result.
Bring back: the explanation, a diff and the checks actually performed.
“Update this feature across the project. Keep the API compatible.”
Independent work can move in parallel. Additions and corrections return to the Bot that holds the project context.
Bring back: related changes, review findings and remaining gaps.
“Compare these approaches and write down a recommendation.”
Keep sources, notes and deliverables with the project. Read documents and code alongside the main conversation.
Bring back: a readable conclusion, source references and open questions.
How you work together
You should not have to manage every Agent turn. The project Bot is your point of contact as work is delegated, corrected and reviewed.
Choose a stage to read the example. This walkthrough is illustrative; it does not start Agents or execute commands.
A project, not a disposable chat
The folder, project memory, goals and history remain available. Long work uses governed context and retrieval rather than relying on one endless transcript.
Work Agents have their own context and bounded goals. The main Bot coordinates additions and questions; execution still follows local permissions.
The Bot explains what changed, what was checked and what remains uncertain. Verification, acceptance and Git integration are distinct facts.
Add context, change direction or ask to stop. User decisions and permissions are not replaced by an Agent saying it can handle them.
Local authority
Models provide cognition and may run with a cloud provider. Peer handles local capability execution, permission decisions and evidence. What a model may receive follows the configured provider and context permissions.
Desktop and CLI share the same local runtime. Models, MCP, Skills and Plugins add capabilities through governed contracts.
Choose your entry point
Choose the project Bot preview, the classic stable release, or the terminal. Read the release notes for platform availability and upgrade guidance.
0.1 preview
The 0.1 preview brings project Bots, a work panel for tasks and child Agents, memory, goals and an independent reading workspace. Optional input suggestions require a dedicated model. Preview software is still evolving.
Open preview downloadsBack up the full data directory before upgrading. Follow the release-specific compatibility notes.
0.0.18
The 0.0 release uses the classic workflow interface. It does not include the default 0.1 project Bot experience shown above.
Open stable downloadsThe current stable and preview channels are separate. Choose the one that matches the experience you need.
Install peer for the TUI and scripted entry points. The rc channel corresponds to the project Bot preview.
CLI guide
Peernpm install -g @peer-agent/cli@rcStable 0.0.18 uses the classic interface. Follow published releases for the current 0.1 preview, platform assets and compatibility notes.
All releases and current assets