Work happens on a copy
Every task is a copy-on-write copy of your folder. The agent changes the copy; your folder changes only when you commit, and undo puts it back.
A sandbox around every command
Commands may write only to the copy. Your credentials, your own folders and the projects beside the workspace stay out of reach.
Judged by what it did
A policy looks at the effects of the work: which files, which git refs, which hosts. Ordinary edits pass, risky ones wait for you, git hooks are denied.
Every connection goes through a proxy
Package registries pass, the agent reaches its own API, and anything else waits for your answer. Every connection is logged.
Secrets the agent never sees
The agent sees a placeholder; the proxy puts your API key into requests to the hosts you named, and nowhere else.
Any folder, not only code
Notes, documents, photos and data work the same way. Kule needs no git, and reads .git as a repository when there is one.
The same from a terminal
kule new ~/code/app # make a task: a copy of the folder
kule run 1a2b3c4d "Fix the failing test" # an agent works in the copy, in the sandbox
kule status 1a2b3c4d # what changed, and what the policy says
kule commit 1a2b3c4d # apply it to the folder, keeping a checkpoint
kule undo 1a2b3c4d # changed your mind? put the folder back
Every command is explained in the CLI reference.