Edge-First Coding Workspace: Editing Live Files Without Waiting for a Container
Anakin resolves workspace reads, search, listings and edits from edge storage first, so a cold container never blocks an edit. The live container is mirrored in the background and each edit reports its mirror status. A workspace file inventory in the prompt and intent-based tool routing keep requests like adding a photo to a live website short.
Frequently asked questions
Why do coding agents feel slow on simple file edits?
Many harnesses boot a sandbox container to find and edit any file. A cold container can take many seconds to wake, and the agent often spends several tool steps searching before it edits.
What does edge-first mean for workspace files?
Files are stored in edge database and object storage. Reads, glob, grep, repository maps and edits resolve there first. The container is a fallback and is kept in sync in the background.
How does the agent know which files exist?
A workspace state inventory listing the most relevant files is placed in the prompt from the first token, so the agent can target a file immediately instead of searching.
Can edge search miss files that exist only in the container?
Files created only inside the live container and not yet synced are not in the edge index. Edge search results say so and point to live-disk inspection when a file is missing.
Sources: live catalog, resource model, integration guide.