RunTrim
FAQ

RunTrim FAQ

Answers about privacy, guarded runs, restore and plan limits.

Trust and privacy

What is RunTrim?

RunTrim is the control, verification and recovery layer for AI coding agents. It gives coding agents scope, memory, finish checks, restore points and continuation prompts while keeping source code local by default.

Does RunTrim upload my source code?

No. Source code stays local by default. Cloud sync stores run metadata only.

What data does RunTrim sync to the cloud?

Run metadata such as verdict, changed file paths, project memory summaries, and restore metadata. Not raw source file contents.

Can RunTrim read .env files or secrets?

RunTrim checks sensitive paths for safety, but does not read or upload env file contents.

Is RunTrim local-first if I never log in?

Yes. Free runs locally with guarded runs, finish verification, and local restore.

Agent workflow

Which agents does RunTrim work with?

RunTrim works with Claude, Codex, Cursor, ChatGPT, DeepSeek, and other coding agents through copy mode or MCP-compatible workflows.

Do I need MCP to use RunTrim?

No. MCP is optional. Copy mode works with any agent UI.

Does RunTrim replace my coding agent?

No. RunTrim is the control, verification and recovery layer around your agent.

How is RunTrim different from agent orchestrators?

RunTrim is not an orchestrator that routes model calls for you. It is a guard layer that adds scope contracts, verification and recovery around the agent workflow you already use.

What is the recommended command flow?

runtrim start runtrim agent "your task" --copy runtrim finish runtrim restore, if recovery is needed

Restore and recovery

Does restore use more agent tokens?

No. Restore is local recovery and does not require another agent run.

Does RunTrim help reduce token waste and speed up coding?

Usually yes. By keeping runs scoped and carrying forward project memory, RunTrim often reduces repeated context loading and shortens rework cycles. Results vary by workflow.

What happens when a run is BLOCKED?

BLOCKED means the run needs review and is not trusted yet. Review the changes, approve a scoped change, or restore.

Is restore local or remote?

Restore apply is local through the CLI. The dashboard shows restore metadata and recovery guidance.

What is restore metadata?

Restore metadata is the run-linked recovery record shown in dashboard history. File recovery still happens locally.

Plans and limits

What is included in Free vs Pro vs Builder vs Team?

Free protects one project locally. Pro adds cloud sync and dashboard history for your main project. Builder adds unlimited projects and CI Gate. Team adds governance controls, with some capabilities marked reviewed access or coming soon.

How is RunTrim different from Git?

Git tracks version history. RunTrim adds run-level control, verification and local restore for AI coding agent workflows before and after changes are made.

Why is cloud history locked on Free?

Free is designed for local-first guarded runs. Pro unlocks cloud run history, memory sync, and restore metadata sync.

When should I upgrade to Builder?

Upgrade when you need multi-project protection, advanced recovery history, and CI merge gating.

Is Team fully live or reviewed access?

Team is reviewed access. Some governance features are live or rolling out, and unfinished capabilities should be labeled coming soon.

Teams and CI

Does RunTrim block risky PRs in CI?

Yes, with runtrim ci check when configured. BLOCKED runs should fail the check.

Are GitHub checks and policies live for all plans?

No. CI and policy depth are plan-gated. Builder unlocks CI Gate, and Team expands governance.

What governance features are live today for Team?

Only show implemented controls as live. Label shared logs, approvals, and policy surfaces accurately if still rolling out.

Next step

Start local with the CLI, then unlock cloud history and governance when your workflow needs it.