- Teams running multiple parallel agent projects that need clean isolation
- Builders who want white-box, editable, rollback-capable agent memory
- Users looking to cut token costs through intelligent model routing
PilotDeck
Open-source agent operating system with WorkSpace isolation, white-box memory, smart routing, and always-on execution.
What is PilotDeck?
PilotDeck is an open-source agent OS from Tsinghua THUNLP, ModelBest, OpenBMB, and AI9Stars, built around WorkSpace-level isolation for files, memory, and skills across projects.
WorkSpace-level isolation
Every project gets its own file system, memory store, and skill set. Parallel work does not interfere, retrieval is bounded, and skills accrete naturally per project.
Without isolation, multiple tasks pollute a shared context; with PilotDeck, projects run in parallel with clean boundaries.Traceable white-box memory
Memory generation, extraction, storage, and retrieval are visible end-to-end. Users can edit or delete entries, pin critical decisions, and one-click rollback via Dream Mode.
When AI mis-remembers, you can pinpoint the offending entry and fix it directly instead of starting a new chat.Smart routing for cost optimization
TokenSaver automatically classifies task complexity and routes simple tasks to lighter models, cutting token spend by up to 70% without sacrificing quality.
Running agents in the background becomes economically viable when you are not burning flagship models on trivial calls.Always-on background execution
After you sign off, the agent keeps discovering candidate tasks, running monitors, and landing deliverables as files with a summary report waiting for you.
Agent work should not stop when you close the laptop.What PilotDeck is built for
Multi-project agent workflows
Use PilotDeck when running agents across several projects simultaneously, with each needing independent files, memory, and skills.
Cost-sensitive agent deployment
Use TokenSaver routing to automatically match task difficulty to the right model tier, dramatically cutting token bills.
Unattended automation
Deploy Always On mode so the agent discovers issues, runs scheduled cron tasks, and produces reports while you are away.
Auditable agent memory
Use white-box memory when you need to inspect, edit, or roll back exactly what the agent remembers per project.
Get started in seconds
curl -fsSL https://raw.githubusercontent.com/OpenBMB/PilotDeck/main/install.sh | bash pilotdeck git clone https://github.com/OpenBMB/PilotDeck.git && cd PilotDeck && npm install && cd ui && npm install && cd .. How it stacks up
PilotDeck is a full agent OS, not just a coding agent
vs coding agentsClaude Code and OpenHands focus on repository-level coding. PilotDeck is a general-purpose agent OS with WorkSpace isolation, routing, memory, and always-on execution.
PilotDeck isolates by project, not by session
vs standard chat agentsStandard agents mix all context in one pool. PilotDeck gives each WorkSpace its own files, memory, and skills so projects never bleed into each other.
Frequently asked questions
What should I check before using PilotDeck?
Start with one WorkSpace in PilotDeck. Inspect how memory is captured and displayed, configure model providers with multiple tiers, enable TokenSaver routing, and test Always On discovery in an idle project.
Is PilotDeck open source?
PilotDeck is listed with AGPL-3.0 based on the official source links in this profile. Re-check the repository, license file, or docs before production use.
Who should evaluate PilotDeck?
PilotDeck is most worth evaluating for teams running multiple parallel agent projects that need clean isolation, traceable memory, and cost-efficient model routing.
What makes PilotDeck different from other agent platforms?
PilotDeck is WorkSpace-first: each project has isolated files, memory, and skills. It also provides white-box editable memory, automatic model tiering (TokenSaver), and always-on background execution — capabilities most agent platforms lack.
Should you use PilotDeck?
- Users who only want a single-chat chatbot with no project structure
- Teams unwilling to review model provider credentials and routing configuration before usage
- Verified 2026-06-03
- License: AGPL-3.0
- Repo: OpenBMB/PilotDeck
- Open-source signal
self hosted, cloud
memory, messages, external services
Self-hostable, MCP
Structured decision data for PilotDeck
This packet is the compact machine-readable view agents should use before following source links or taking action.
memory, mcp, workflow orchestration
open source, self hosted, mcp compatible
self hosted, cloud
memory, messages, external services
Coding agent workflow, Reusable skill workflow
What PilotDeck does
What it is
PilotDeck is an open agent OS to evaluate by project isolation and memory architecture: how it separates work into WorkSpaces, whether memory is white-box and editable, how it routes tasks to the right model tier, and whether it can run background discovery and cron jobs.
Why it matters
PilotDeck matters because it addresses the gaps in current agent platforms: memory that is opaque and uneditable, token costs that do not differentiate between trivial and complex tasks, and agents that stop working when you walk away. Its WorkSpace-first design and three pillar capabilities (white-box memory, smart routing, always-on) are practical explorations of these open problems.
How to evaluate it
Start with one WorkSpace in PilotDeck. Inspect how memory is captured and displayed, configure model providers with multiple tiers, enable TokenSaver routing, and test Always On discovery in an idle project. Expand from sandbox projects into production automation after verifying isolation and cost controls.
Known metadata and operating surface
These fields are separated from editorial interpretation so agents can reason over facts and missing checks.
Where PilotDeck fits in an agent stack
Coding agent workflow
PilotDeck has multiple signals for coding agent workflow, including matching tags, capabilities, category, or positioning.
- Run a small repository change and inspect the diff, tests, and rollback path.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Reusable skill workflow
PilotDeck has multiple signals for reusable skill workflow, including matching tags, capabilities, category, or positioning.
- Run one skill end to end and check whether it produces evidence or structured output.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Connector or protocol layer
PilotDeck has at least one signal for connector or protocol layer, but should be checked against a real task before adoption.
- Connect one low-risk service, then inspect schemas, auth scope, errors, and logs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Local or private AI stack
PilotDeck has at least one signal for local or private ai stack, but should be checked against a real task before adoption.
- Verify hardware requirements, data path, storage, and whether all calls stay in your environment.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Memory or RAG workflow
PilotDeck has at least one signal for memory or rag workflow, but should be checked against a real task before adoption.
- Create, update, retrieve, correct, and delete memory or retrieval objects with real data.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Browser automation
PilotDeck is not primarily positioned for browser automation in the current metadata.
- Run one non-sensitive website task and inspect clicks, waits, retries, and changed URLs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
What an agent should inspect
Likely inputs
- Repositories, files, issues, terminal output, and test results
- Documents, user facts, entities, context, or retrieval queries
- Tool schemas, API requests, service resources, and auth scopes
- Prompts, messages, documents, images, or model inputs
- Official setup instructions and a small real workflow
Likely outputs
- Diffs, commits, explanations, test results, or review notes
- Retrieved context, memory updates, graph relations, or citations
- A decision on whether this resource fits the target workflow
Sources, claims, and missing checks
Claims are marked separately from source links so future crawlers and reviewers can update them without rewriting the page.
Repository source for code, license, issues, releases, and implementation details.
Homepage homepageOfficial or project-controlled source for this resource profile.
Docs docsDocumentation source for setup, API shape, and operational behavior.
PilotDeck is listed as open source.
License metadata: AGPL-3.0PilotDeck has a recorded GitHub repository: OpenBMB/PilotDeck.
Resource facts and GitHub source link.PilotDeck supports these recorded deployment modes: self hosted, cloud.
OpenAgent decision signal metadata.PilotDeck is tagged with memory, mcp, workflow orchestration capabilities.
OpenAgent capability taxonomy.- Repository freshness has not been recorded.
How to start evaluating PilotDeck
Inspect repository
Check license, recent activity, issues, examples, and security-sensitive code paths.
Open sourceOpen Homepage
Start from the official source before adopting third-party instructions.
Open sourceRead setup docs
Use docs as the source of truth for installation and supported interfaces.
Open sourceOne-line install (macOS / Linux)
Auto-installs Node.js 22, clones the repo, installs dependencies, and builds the frontend.
curl -fsSL https://raw.githubusercontent.com/OpenBMB/PilotDeck/main/install.sh | bash Start the server
Starts the PilotDeck server at http://localhost:3001
pilotdeck Alternatives and nearby resources
Use related resources to compare category fit, license, deployment model, and first-workflow behavior.
Common questions about PilotDeck
What should I check before using PilotDeck?
Start with one WorkSpace in PilotDeck. Inspect how memory is captured and displayed, configure model providers with multiple tiers, enable TokenSaver routing, and test Always On discovery in an idle project.
Is PilotDeck open source?
PilotDeck is listed with AGPL-3.0 based on the official source links in this profile. Re-check the repository, license file, or docs before production use.
Who should evaluate PilotDeck?
PilotDeck is most worth evaluating for teams running multiple parallel agent projects that need clean isolation, traceable memory, and cost-efficient model routing.
What makes PilotDeck different from other agent platforms?
PilotDeck is WorkSpace-first: each project has isolated files, memory, and skills. It also provides white-box editable memory, automatic model tiering (TokenSaver), and always-on background execution — capabilities most agent platforms lack.