💡 Workspace Safety Snapshots: Avatar-Guided Rollback for Fearless Non-Technical Agent Use

[github-actions[bot]]

Summary

Before executing any workflow that modifies files, TalkTerm automatically creates a lightweight workspace snapshot — a git branch for git workspaces, or file-level backup for non-git directories. If a user says "undo everything from that last session," the avatar explains what changed, previews the rollback as a visual diff, and restores the snapshot. This wraps git's power in conversational UX that non-technical users can safely operate, transforming the fear of irreversible AI actions into confident delegation.

Market Signal

Industry best practice in 2026 recommends "ephemeral staging workspaces" and "verdict-vs-action separation" for AI agent safety (fast.io, DEV Community rollback guides). McKinsey's State of AI Trust 2026 identifies fear of irreversible AI actions as the #1 adoption barrier for non-technical knowledge workers. No consumer AI desktop agent — ChatGPT, Fazm, Manus — offers avatar-guided workspace rollback. Enterprise tools like nbh.co discuss agent undo capabilities but only for technical users via CLI. This is a trust-building differentiator.

User Signal

The PRD targets non-technical user independence with pre-action confirmation (FR20) and error recovery (FR34-35), but lacks a "full undo" safety net for when a workflow produces undesired results across multiple files. The onboarding initiative (#333-338) builds first-session confidence, but workspace snapshots sustain it across ongoing use. The target persona (Sarah the PM from Journey 1) needs to know that experimenting with AI agent workflows is safe — "try it, and if you don't like the result, just say 'undo.'"

Technical Opportunity

Git workspaces (the primary use case per FR52-53) support lightweight branching natively with near-zero disk cost. Implementation: before agent workflow execution, create a timestamped snapshot branch (talkterm-snapshot/2026-09-25T14:30:00), log branch name in the session audit trail (FR27-29). Rollback = avatar-narrated git checkout with diff preview in OutputPanel (FR45 document display mode). For non-git workspaces, fall back to file-level backup of agent-modified files in a hidden .talkterm-snapshots/ directory. Touches the storage bounded context (main/storage/) for snapshot management and agent bounded context (main/agent/) for pre-workflow snapshot triggers.

Assessment

Dimension	Score	Rationale
Feasibility	high	Git branching is native and lightweight; non-git fallback uses simple file copy of modified files tracked via audit trail
Impact	high	Directly addresses the #1 non-technical user adoption barrier (fear of irreversibility); unique avatar-guided UX
Urgency	high	Trust is a prerequisite for adoption — must be in place before targeting non-technical user independence metrics

Adversarial Review

Strongest objection: Snapshots accumulate disk space over time. Non-git workspaces are harder to snapshot reliably. Complex state (databases, external systems) cannot be rolled back.

Rebuttal: Git branches are near-zero cost (pointers to existing commits). Implement auto-cleanup of snapshot branches older than 7 days (configurable). For non-git workspaces, only back up files the agent actually modified (tracked via audit trail FR27-29) — not full directory copies. Explicitly scope rollback to local file changes only — the avatar transparently communicates that external system actions (API calls, PR creation) cannot be undone. This honest scoping builds rather than undermines trust. Users who know the boundaries of undo feel safer than users promised unlimited undo.

Suggested Next Step

Define the snapshot lifecycle (creation trigger, retention policy, auto-cleanup schedule). Design the avatar rollback conversation flow — diff preview, selective vs. full rollback options, and verbal explanation of what changed. Create a tech spec covering git snapshot branch naming convention, non-git file backup strategy, and integration with the audit trail (FR27-29).