ClearFile recovery for projects that are not Git repositories
ClearFrame records source files, untracked files, binaries, executable permissions and symlinks before a task touches the project, so changes survive before git init.
Engineering
ClearFrame Engineering — How the agent workspace is built
Technical notes on the mechanisms behind ClearFrame, with the limits stated alongside the capability.
Last updated
Engineering notes on the design decisions behind ClearFrame: how file recovery works without version control, how an unattended task's spend is bounded, how the permission model handles long-lived processes, and how an agent is permitted to modify its own source. Each note documents the mechanism, its limits, and the failure mode it exists to prevent.
Bounding what an autonomous agent can spend
ClearFrame offers token ceilings and percentage-of-plan stops so an unattended run can be capped. The stop is measured, not pre-emptive, and the interface says so.
Designing the permission model for a coding agent
Every ClearFrame task runs at one of three access levels, and changing the level closes the task shell so the setting you pick is the setting that applies.
Letting an agent modify its own source code
The ClearFrame Self-Host workflow edits its own source, runs the tests and verifies the installed build before promoting. A failed check can restore the previous build.
Where an agent gets its instructions, and how to see them
ClearFrame loads project instructions into every task and shows them in a Memory panel, including where each came from, so the context behind a decision is readable.
What an agent can reach, and what it must be given first
Skills, MCP servers and the provider catalog decide what a ClearFrame agent can do. A capability being listed is not the same as it being configured.
Why the browser workspace does less than the app
The web app is coming soon. This engineering note describes its browser workspace design and limits: no terminal, no repository access, and a preview with network off.
Publishing a checksum is not the same as publishing a build
Every ClearFrame artifact is listed with its version, byte count and SHA-256, and the download page states when a build is a preview rather than a signed release.
What survives a restart, and what a restart ends
A ClearFrame task keeps its goal across app restarts and resumes from a saved checkpoint. The operation running when the process stops does not survive.
Running two agents on one project
Each ClearFrame task works in an isolated copy of the project and nothing reaches the working tree until it is integrated, which is what makes parallel work safe.
Reviewing AI-generated code before it reaches the main branch
ClearFrame snapshots a project before a task's first tool use and keeps changes in an isolated copy, so review runs against a recorded baseline.
Product documentation is at Docs and release notes at Updates. These notes are also published as an RSS feed.
Try the mechanism.
ClearFrame is free to start. Run a task in an isolated workspace and review the changes before you integrate them.