Checkpoints functionality has disappeared - cause unknown

[magicbrighter]

App Version

v3.21.0

API Provider

DeepSeek

Model Used

DeepSeek V3

🔁 Steps to Reproduce

Problem

The Checkpoints feature that was previously available in the application has suddenly disappeared. I'm unable to locate or access this functionality anywhere in the current interface.
Expected Behavior

The Checkpoints feature should be accessible and functional as it was before.
Actual Behavior

The Checkpoints functionality is completely missing from the interface. I cannot find any trace of this feature in the current version.

💥 Outcome Summary

Request

Could you please help identify:
Whether this is an intentional removal or a bug
If it's temporary, when the feature might be restored
If there's an alternative way to access this functionality

📄 Relevant Logs or Errors (Optional)

[dosubot]

There’s no indication in the documentation or release notes that the Checkpoints feature was intentionally removed or modified in v3.21.0—it should still be present and enabled by default docs. The most common reasons for it disappearing are configuration issues: Checkpoints require Git to be installed and available on your system, and the feature can be toggled in Roo Code’s settings under the “Checkpoints” section docs.

I recommend verifying that Git is installed and checking your settings to ensure “Enable automatic checkpoints” is turned on. If Git is missing or misconfigured, or if the feature was accidentally disabled, Checkpoints won’t appear in the interface. There’s no alternative documented way to access the feature if it’s missing from the UI. If everything looks correct and it’s still missing, this may be a bug introduced in v3.21.0, but there’s no documentation confirming that yet.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[daniel-lxs]

Thanks for reporting this! To help us investigate further, could you provide a bit more info?

• What version of VS Code are you using?
• What type of workspace are you in (e.g. single folder, multi-root, remote, etc.)?
• Do you have Git installed on your system?
• Have you tried using Roo Code in a different workspace to see if the issue persists?
• Can you share the exact steps you were following before the Checkpoints feature disappeared?

Once we have a bit more context, we can better determine whether this is a bug or something else. Appreciate the help!

[aprpure]

I have the same issues.

I've noted the details you provided:

• VS Code Version: 1.101.1 (user setup)
• Workspace Type: Single folder
• Git Installed: Yes
• Tested in a different workspace: Yes, the issue still occurs.
• Previous Version using Checkpoints: Roo Cline v3.19.6
• Upgrade Trigger: From Roo Cline v3.19.6 to Roo Code v3.21.5

[m-marie1]

I've had the same issue only with a specific workspace (a parent folder containing multiple folders, e.g. the frontend and backend, parent isn't a git repo).

It's probably because of this update introduced in Release v3.19.7:
"Disable checkpoint functionality when nested git repositories are detected to prevent conflicts."

Version 3.19.6 works for me.

[NaccOll]

I encountered a similar issue before and submitted a pull request to resolve it. See #6359

The issue occurs because checkpoint initialization has been changed from synchronous to asynchronous. If the checkpoint initialization is not complete when the AI first modifies a file, checkpointing will be disabled for that task. In larger projects, this problem often occurs.

src\core\assistant-message\presentAssistantMessage.ts:532-536

	if (recentlyModifiedFiles.length > 0) {
		// TODO: We can track what file changes were made and only
		// checkpoint those files, this will be save storage.
		await checkpointSave(cline)
	}

src\core\checkpoints\index.ts:194-215

export async function checkpointSave(cline: Task, force = false) {
	const service = getCheckpointService(cline)

	if (!service) {
		return
	}

	if (!service.isInitialized) {
		const provider = cline.providerRef.deref()
		provider?.log("[checkpointSave] checkpoints didn't initialize in time, disabling checkpoints for this task")
		cline.enableCheckpoints = false
		return
	}

	TelemetryService.instance.captureCheckpointCreated(cline.taskId)

	// Start the checkpoint process in the background.
	return service.saveCheckpoint(`Task: ${cline.taskId}, Time: ${Date.now()}`, { allowEmpty: force }).catch((err) => {
		console.error("[Task#checkpointSave] caught unexpected error, disabling checkpoints", err)
		cline.enableCheckpoints = false
	})
}