OPEN SOURCE
Build your idea.
Keep control.
Plan the work. Build with your coding tool. Review every change.
How Foundry works
Team invitationsExample workflow
Define the problem
Find the requirements and open questions.
Team invitations
- Who can send an invitation?
- What happens when a link expires?
- What does a new teammate see?
Example, not a live session. Handoff saves a local summary; it does not publish.
See the workflowInstall
Start with your tools.
Requires Node 24+, npm and Git.
Choose a provider for your project.
Terminal
npm install -g @dabhiram13/foundry
foundryYour work
Pick up where you left off.
- Approve the direction
- Plan and design need your approval before building.
- Keep your progress
- Tasks, decisions and handoff notes carry over.
- Check current code
- Changed inputs need fresh checks.
Questions?
Does Foundry replace my coding tool?
No. The connected workflow uses your coding tool. A built-in browser workspace and PR follow-up are not available yet. See what works today.
Is it just for running checks?
No. Foundry connects research, plans, design, coding and review. You approve the plan and design.
Which provider can I use?
The terminal uses compatible provider adapters. The source connection uses your OpenCode model and account. See the provider guide.
Does my code stay on my computer?
Progress is saved locally. Your provider may receive code and task context. Local commands run with your account’s permissions, not in a sandbox.
Will Foundry publish the product for me?
No. Handoff saves a local summary. You decide when and where to publish.