DevState
Git-backed sessions, checkpoints, and project context for AI-assisted development in VS Code.
DevState keeps the context behind your work close to the editor. Start a focused development session, save Git-backed checkpoints, restore a known state when needed, and copy a current Markdown briefing for an AI coding assistant. It is local-first and uses the same .devstate workspace as the DevState CLI and MCP server.
Why DevState?
AI coding tools are useful only when they have the right project context. DevState gives you a durable record of what you are doing and safe points to return to:
- Keep momentum — record the intent of the current session instead of reconstructing it later.
- Checkpoint safely — capture Git-backed working state with optional notes.
- Restore deliberately — choose a checkpoint and confirm before the working tree changes.
- Brief any assistant — copy current project context as Markdown for Claude, Cursor, Windsurf, Copilot, or another coding assistant.
- Stay local-first — no account or AI-service connection is required.
Install
Install DevState from the Visual Studio Marketplace, or search for DevState in VS Code's Extensions view.
For an offline or managed installation, download the release .vsix and run Extensions: Install from VSIX... from the Command Palette.
Requirements
- VS Code 1.90 or later
- An open workspace folder
- Git on
PATH for checkpoints, restore, and working-tree status
Quick start
- Open the folder you want to track in VS Code.
- Select the DevState icon in the Activity Bar.
- Select Initialize Workspace.
- Select Start Session and describe the work.
- Select Create Checkpoint at useful stopping points.
DevState stores its local state in .devstate. Restoring a checkpoint always asks for confirmation. Force Restore can overwrite uncommitted changes.
Features
- Overview — workspace, active session, Git branch, working-tree state, and latest checkpoint.
- Active Session — intent, elapsed time, and checkpoint count.
- Checkpoints — saved checkpoints and their details.
- Status bar — the active session, or
No session.
- Live refresh — views update when
.devstate changes, including changes from the DevState CLI.
- AI-ready context — copy a current Markdown briefing without leaving VS Code.
How it compares
| Need |
Manual notes or Git stash |
DevState |
| Remember why work started |
Separate, easy to forget |
Session intent in the workspace |
| Save a working point |
A stash or ad-hoc commit |
Named Git-backed checkpoint with notes |
| Return to a prior state |
Recall the correct stash or commit |
Pick a checkpoint and confirm restore |
| Brief an AI assistant |
Reconstruct context manually |
Copy current context as Markdown |
DevState complements Git; it does not replace branches, commits, code review, or your normal source-control workflow.
Commands
Open the Command Palette and run:
| Command |
Description |
DevState: Initialize Workspace |
Create a DevState workspace in the open folder. |
DevState: Start Session |
Start a session and record its intent. |
DevState: Close Session |
Close the active session. |
DevState: Create Checkpoint |
Save a Git-backed snapshot of current work. |
DevState: Restore Checkpoint |
Choose and restore a checkpoint. |
DevState: Show History |
Show the session and checkpoint timeline in the DevState output channel. |
DevState: Show Status |
Show workspace, session, Git, and checkpoint status. |
DevState: Copy Context for AI |
Copy current DevState context as Markdown. |
The Refresh and Open Panel actions are available from the DevState view itself.
Troubleshooting
- Initialize Workspace is unavailable or nothing appears: open a folder, not an empty VS Code window.
- Checkpoint or restore fails: make sure Git is installed and available on
PATH, then run DevState: Show Status for the current repository state.
- No active session: run
DevState: Start Session before creating a checkpoint.
- Views look stale: use the Refresh button in the Overview view.
FAQ
Does DevState send my code or data to a service? No. DevState is local-first, requires no account, and does not call AI services.
Can I use the CLI and MCP server too? Yes. They use the same .devstate workspace, and the extension refreshes when that workspace changes.
What does a checkpoint contain? A Git-backed snapshot of the working state, with optional notes. Review the restore confirmation carefully before applying one.
Contributing
Issues and contributions are welcome. Read the contributing guide, then open an issue or pull request in the DevState repository.
Links
