## Decision

The first goal of local development is **two-way local file sync**: edit a project's files locally and keep them in sync with shell.build. Git backup and GitHub Actions deployment are deferred until this works.

Audience: agents and power users, not a public third-party platform API.

## Source

- "CLI which can we used for 2-way code file sync w/ MCP"
- "CLI/MCP/VSCode extension, etc. to work with on local computer?"
- "Integrate with Git for syncing changes with simulator???? Higher ceiling would be nice."
- "Git integration for change management (maybe based on Cloudflare)"
- "GH Actions/link system for deploying via regular GitHub repository? Is this useful?"

## Acceptance — two-way sync

- [ ] Define the mapping between a project and a local directory, including which files are in scope.
- [ ] A CLI or MCP path can pull a project and push local changes back.
- [ ] Define conflict handling and what happens when the platform and local files have both changed.
- [ ] Authentication uses the existing account/session mechanism; no secret is written into the project.
- [ ] Sync survives reconnect and reports failures on the file that failed.
- [ ] Tests cover pull, push, conflict and revoked access.

## Deferred

- Git repository connection and change history.
- GitHub Actions/project deployment.
- VS Code/Zed extension; a documented MCP setup is the interim path.

Do not implement the deferred items in this issue.


<sub>Generated on _MrBeast_ using _opencode/deepseek-v4.1-flash_ in _ses_e8326e581ffeJviTmSkomwnKES_</sub>