Editing generated code
In short
Edit anything you like — your changes are checkpointed as their own version before the next agent turn — but code you intend to keep hand-writing belongs in //!DEV or //!SAFE, or a later turn may rewrite it.
It is your repository. You can edit any file at any time, from the studio or from your own checkout.
Your edits are never silently swallowed
Before an agent turn starts, Sapilon checkpoints any uncommitted changes as their own version, attributed to you. Two consequences worth knowing:
- The agent’s turn starts from a clean tree, so its diff is only its own work.
- Undoing that turn rolls back the agent’s changes, not yours.
But //!AUTO code can be rewritten
A hand edit inside //!AUTO is kept — and then a later turn that touches the same area may
replace it, because that zone says the agent owns the file. If you intend to keep hand-writing
something, move it:
//!SAFE— you still get agent proposals, but every change comes to you as a diff.//!DEV— the agent stops touching it at all.
Moving the code is the durable fix. Telling the agent “don’t change this file” works for one conversation; the marker works forever.
Platform updates
Sapilon periodically brings projects in line with evolving templates via an upgrade-aware
diff. It follows the same rules: //!AUTO is updated in place, //!SAFE comes as a
proposal, //!DEV is left alone. Conflicts are left in the tree for you to resolve rather
than being force-resolved.
Getting back
Every version is restorable, and restoring creates a new version rather than deleting history — nothing you did is destroyed by going back to an earlier state.
Next: When the agent stops · Your first Ask