Core Workflows

Checkpoints & Rollback

DevcoreAI automatically saves a snapshot after every file change. Restore files, conversation, or both — at any point in the task.

How Checkpoints Work

Each time DevcoreAI writes or deletes a file, it saves the complete workspace state as a commit in a shadow Git repository — a hidden repo managed entirely by DevcoreAI, completely separate from your project's own Git history. Your commits, branches, and remotes are never touched.

Checkpoint timeline — a typical task

●checkpoint 3Added auth.routes.ts · POST /auth/refresh

●checkpoint 2Modified auth.service.ts · refreshToken()

●checkpoint 1Modified authenticate.ts · token validation

●task startWorkspace snapshot before task began

Created automatically after every agent file change — no action needed
Stored in a shadow repository separate from your project Git
Captures all files including those not tracked by your own Git
Persists across editor sessions — available after restart
Never pushed to any remote — local to your machine only

Reviewing Changes in the Diff Editor

Before any file is written, DevcoreAI opens a diff editor showing the proposed changes. Added lines are highlighted in green, removed lines in red. You have three options:

src/auth/auth.service.ts

+4 / -2

async login(credentials: LoginDto) {

- const token = this.jwt.sign(payload);

- return { token };

+ const accessToken = this.jwt.sign(payload, {expiresIn: '15m' });

+ const refreshToken = this.jwt.sign(payload, {expiresIn: '7d' });

+ await this.saveRefreshToken(userId, refreshToken);

+ return { accessToken, refreshToken };

}

✓ Accept✗ Reject↩ Request Changes

Three Restore Options

Hover over any message in the task to reveal the restore button. Clicking it gives you three choices depending on what you want to recover:

Restore Files

Use when: The conversation is still useful but the code changes broke something.

Result: Files revert to this checkpoint. Conversation history is kept — you can guide the agent to try a different approach.

Restore Task Only

Use when: The code changes are good but the conversation went off track.

Result: Files stay as they are. Conversation resets to this point — you can redirect from here.

Restore Files & Task

Use when: You want a complete clean slate from this point forward.

Result: Both files and conversation reset to this checkpoint. Everything after is discarded.

Restoring a checkpoint is irreversible. All task messages and file changes after the selected checkpoint will be permanently discarded. DevcoreAI shows a confirmation dialog before proceeding.

Requirements & Behavior

Project Git required?No. Checkpoints use a shadow repository maintained by DevcoreAI, independent of your project Git.

Shadow Git requires Git?Yes — Git must be installed on your machine. The shadow repo is created automatically on first use.

Affects my commits?Never. The shadow repo is completely separate. Your branches, history, and remotes are untouched.

Untracked files captured?Yes — the shadow repo captures all workspace files, including those not tracked by your own Git.

Multi-root workspaces?Not supported. Checkpoints only work in single-folder workspaces.

Disable checkpoints?Settings → Feature Settings → toggle 'Enable Checkpoints'.

Checkpoints & Auto-Approve

When auto-approve or YOLO mode is enabled, file changes are applied without stopping for diff review. Checkpoints are still created after each step, so you can always roll back even if you weren't watching.

A common pattern: enable auto-approve for speed, let the task run, review the final result, and use checkpoints to restore to the last good state if anything went wrong.

← Plan & Act Modes Auto-Approve & YOLO