PPIO · deepseek/deepseek-v4-pro
Local-first · Bring your own key
One entry point,
your whole AI dev environment.
Move from agent to provider to protocol verification in one path. The demo below is live — real scanning, writes and backups happen in local BootAgent.
0.6.2 · unsigned technical preview · currently macOS Apple silicon / ARM64
Select agents
Choose the development tool to install and configure. One per run
- 1Agent
- 2Select a profile
- 3Provider
- 4Model
- 5Review
- 6Install
Select agents
Choose the development tool to install and configure. One per run
Agent install source
A mirror is the default here based on the example system region. You can switch back to the official source
Connection testing is optional. You can continue directly to model selection
Will process
Provider
Local writes
View install log
$ npm install -g --registry=https://registry.npmmirror.com/ @anthropic-ai/claude-code $ claude --version
Command-line Agent
1 totalDesktop Agent
0 totalInstall a desktop Agent from the guided flow
The website demo does not open a local terminal.
One activation path
Detect, connect and verify — with every step explained.
Configuration, backups and credentials stay on your machine. The protocol an agent actually needs is verified before anything is written.
Read the environment
Installed, needs setup, official flow only — three states listed separately rather than flattened into one checkmark.
Connect a provider
Filter by the protocol an agent needs, or point it at your own endpoint. Every compatibility level is named.
Verify and review
Once verification passes: Ready state, the paths written, the backups taken, and the next command to run.
Compatibility Explorer
A real catalog, not a static compatibility poster.
10 agents (8 command-line, 2 desktop), 4 public providers, and independent compatibility for OpenAI Responses, Anthropic Messages and Chat Completions.
Understand the flow in the demo, then activate it locally.
Download BootAgent for local detection, configuration backups and protocol verification. Team baselines and internal delivery still never take custody of API keys.