Replies: 2 comments 1 reply
-
|
We've got a script at work which takes an issue number, creates a branch following our conventions from that issue, we'll then check that out as a git worktree, swap you into the work tree, and then launch nono from within that. It also sets environment variables with the issue number and will launch Claude in danger mode, running a specific custom skill that knows how to then start working on that issue. We are able to resume to a certain extent, because we keep track of what's going on in a folder within the work tree. If you run the same command again, you get put back in that and it's able to read that folder of information. I think being able to resume an actual session would be useful, it would be nice if environment variables were maintained in the session It would also be nice to be able to set our own session names (we'd use our issue id for example) |
Beta Was this translation helpful? Give feedback.
-
|
Sign me up 👋🏽 I had been playing with tmux and locked sessions and an agent skill to drive them from an orchestrator agent so this being embedded in a Nono Agent Skill is a no-brainer for me. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Testers wanted for a preview feature of how nono can manage sandboxed processes as long-lived sessions. You can start a session, detach from it, come back later, reattach, and stop it when you are done. The sandboxed process keeps running whether you are watching it or not.
This is useful when running AI agents, build pipelines, or any long-running task where you want kernel-enforced sandboxing, snapshot rollbacks - without being glued to the terminal.
Full guide to accessing the preview and user guide on commands available
Runtime Sessions in nono.pdf
Beta Was this translation helpful? Give feedback.
All reactions