Your AI build team in the terminal.
Projectinator turns an app idea into working files. A PM model plans the backlog, role-matched models design and code it, and a tester verifies the result in a headless browser while you follow every task and cost.

Why Projectinator
Plan before coding.
A project-manager model turns your idea into a dependency-aware Scrum backlog. You can review the plan before the build team starts writing files.
Use the right model for each job.
Planning, design, development, and testing route by capability. Assign preferred models yourself or let Projectinator use the configured provider defaults.
Test the result, not the promise.
The tester opens the generated web app in headless Chromium, checks for runtime errors, and sends failures back to the developer for another bounded pass.
Built for observable, controlled runs
The cockpit exposes the work instead of hiding it behind a single progress spinner.
Scrum planning
A routed backlog with epics, task dependencies, editable boards, and quick or deeper council-assisted planning.
Role-based model team
PM, designer, developer, and tester roles can use different Anthropic, OpenAI, Gemini, or OpenRouter models.
Real file generation
The developer works in a local, git-versioned workspace and creates multi-file HTML/CSS/JS or React CDN projects.
Browser test gate
Playwright and Chromium check generated apps over HTTP and file URLs, including JavaScript and console failures.
Live terminal cockpit
Follow the Kanban board, standup, task status, running spend, and budget from one Ink-based terminal interface.
Cost and budget controls
See provider-reported usage, per-task cost, estimates that self-calibrate, and a cap that halts before projected overspend.
Install
Start with one command
Projectinator is a CLI, not a library. Run it directly with npm, then add your provider key under Settings and choose New build.
Browser testing and live preview additionally require npx playwright install chromium.
npx projectinatornpm install -g projectinator
projectinatorProviders and cost
Your models. Your budget.
Bring keys for Anthropic, OpenAI, Google Gemini, or OpenRouter. Different roles can use different providers, with model assignments and fallback behavior controlled in Settings.
- Estimates before executionPredicted task cost before the build starts.
- Actual usage while runningProvider-reported token cost by task and session.
- A hard stopping pointThe build halts when projected spend would cross your cap.
Local data and execution
Know what runs where.
Keys, build state, cost calibration, templates, and generated workspaces stay on your machine. API requests go directly to the provider you select; Projectinator does not operate an intermediary backend.
Generated code is not sandboxed
Build roles can use shell and file tools inside the workspace as your user. Inspect generated code and commands before trusting or deploying them.
Open source and inspectable
Projectinator is published under the MIT license. Read the implementation, report issues, or adapt the workflow for your own build process.
Projectinator FAQ
What is Projectinator?+
Projectinator is an open-source terminal app that coordinates AI models as a small build team. It plans a backlog, writes project files, tests web apps, and tracks the work from a live cockpit.
Do I need my own API keys?+
Yes. Add an Anthropic, OpenAI, Google Gemini, or OpenRouter key in Settings. Keys are stored locally in ~/.projectinator/config.json with owner-only permissions.
How much does a build cost?+
You pay your selected AI providers directly for token usage. Projectinator shows estimates before work, provider-reported actual cost while running, per-task spend, and a configurable budget cap.
Can I choose which models it uses?+
Yes. Settings lets you choose a preferred provider and assign models to roles. OpenRouter users can browse its model catalog, and Projectinator can fall back to another configured provider after an error.
Where are generated files stored?+
Each build gets a local workspace that is initialized as a git repository. Projectinator creates a commit for each completed task so you can inspect history or undo work.
How does browser testing work?+
Install Chromium with Playwright to enable the full test and preview workflow. The tester loads the app headlessly over HTTP and file:// and reports runtime or console failures.
Can I stop and resume a project?+
Yes. Build state is saved locally, and finished tasks can be seeded back into a resumed run so completed work is not repeated.
Is generated code sandboxed?+
No. Build roles can use shell and file tools inside the project workspace as your local user. Review generated code and commands with the same care as any code you run locally.
Which systems are supported?+
Projectinator requires Node.js 20 or newer. The repository does not currently declare or guarantee a specific operating-system support matrix.
Is Projectinator open source?+
Yes. Projectinator is available on GitHub and npm under the MIT license.
Give your AI team a backlog.
Open source, MIT licensed, and ready to run with Node.js 20 or newer.
Node.js 20+ · Bring your own API keys · API usage billed by your providers