Kule needs testers: run AI agents on a copy of your folder, then tell me what broke
Last week I wrote about Kule , the open-source tool I'm building. Your comments turned into real changes, so this time I'd like to ask for something more specific: try Kule on your own computer, and tell me what happened. Kule in one paragraph Kule is a control room for AI agents that work on your

Last week I wrote about Kule, the open-source tool I'm building. Your comments turned into real changes, so this time I'd like to ask for something more specific: try Kule on your own computer, and tell me what happened.
Kule is a control room for AI agents that work on your folders. You point an agent (Claude Code, Codex, Gemini, or any agent that speaks ACP ) at a folder. Kule gives it a copy-on-write copy of that folder inside an OS sandbox, looks at what every command really changed, and lets nothing reach the real folder until a policy, or you, says so. Every commit can be undone. It has a CLI and a desktop app, it's written in Rust, and it's Apache-2.0.
That post covered 0.2.0-preview.1. The latest is 0.2.0-preview.14. Some of the bigger changes:
Some of these came straight from comments on the first post:
Thank you to everyone who asked those questions.
I wrote a short testing guide with six scenarios. Each takes 5 to 20 minutes, and you can pick any of them:
At the end of each one, there's only one question: what happened that you didn't expect? A confusing step, a policy that asks too often, a tool that breaks inside the sandbox, a slow copy: all of it is useful. "Everything worked" is useful too.
Kule is tested on a handful of machines. If yours is one of these, a short report is worth a lot:
Open an issue at github.com/kulehq/kule/issues/new/choose and pick one of the forms: Bug report, Test report or Idea or change. Questions are welcome in Discussions, or right here in the comments.
Issues are public, so please leave out API keys, tokens, private paths and anything else you wouldn't publish. The forms remind you.
If you find a way past one of Kule's boundaries, please don't post it publicly. Report it privately, as SECURITY.md explains. The fix is made in private and released first, and the advisory credits you unless you'd rather it didn't.
I read every report. A fix ships in the next preview, and its issue says which one. The CHANGELOG lists what each preview changed.
Thanks for reading, and thanks in advance to anyone who gives it 15 minutes. 馃檹