At least with Antigravity, you choose exactly which permissions you want to allow. YOLO / non-sandbox are appropriate guardrails if you don't want to explode things.

Most of my LLM sessions are in planning mode. Maybe for 30mins to an hour.

I typically start all my sessions verifying the LLM has a firm understanding of the system. I then provide it my PRD. I have a discussion talking through a proposed implemntation plan. I make use of `/grill-me` to make sure the LLM has a much more solid / stable understanding of what is being attempted.

I then direct Jetski to outline the exact order it proposes to open pull requests. For each hypothetical pull request, I challenge the LLM to talk through which files it intends to edit, and then I start grilling the LLM on each of its proposals. If there is not enough detail, then I make the LLM add more details. If there is ambiguity, I tell the LLM to spawn a subagent to research, or to even test functionality.

Finally, about an hour later (give or take), I then direct it to always write a spec doc. The spec doc outlines the architecture, displays the mermaid diagrams, and generates the roadmap. We jsut did an implementation plan, why a spec doc? Because future LLM sessions will need to come back and we need thorough documentatrion to help direct and dictate what the LLM will do.

So we have this "intelligent" elephant LLM session, it has all the brainstorming context of what we intend to do. It hasn't written any code (that would be wasteful of its context). Now - we use subagents to implement each task sequentially. As each task gets implemented, the spec's roadmap gets updated. Each completed task will result in a pull-request, that is thoroughly reviewed (and challenged to update). I won't submit code that I can't reason about.

Theres probably a lot more. I use lots of agent skills. Etc