Allow queueing /new or /compact commands

Resolved 💬 6 comments Opened Jan 12, 2026 by darinkishore Closed Apr 22, 2026

What feature would you like to see?

Currently, you can only run /new or /compact when an agent completes their task entirely .

instead, for more powerful orchestration capabilities, if we can queue /new or /compact that would be lovely.

example, i have the following prompt :

Please implement phase 2 fully ! Please first use bd prime; then run bd ready.

  Then, please look thru the realtime epic, and run the core beads/jj workflow to work through every bead in phase 2--you can do this just by finishing a bead, and running bd ready next.
Show, claim, and properly Finish every phase 2 bead in full. Ensure that you fulfill all acceptance criteria per bead. 

 Be thorough and precise. You may fix other technical debt or confusions if you find them.

For a concise overview of the full realtime system with proper types, please first reference beads_stateright_models/src/realtime_types_sketch.rs .
And very importantly, if anything is ambigious, please refernece the original plan (REALTIME_PLAN.md for more information). 

  please create new commits for each bead (jj workflow) . make sure cargo check and clippy are happy before moving on to the next task . 

  If you are creating new types, first read docs/philosophy/type_design.md .
  If you are handling errors, please read docs/philosophy/error_design.md .
  If you are creating traits, please read docs/philosophy/trait_design.md .
  If you are writing tests, please read docs/philosophy/test_design.md.

  Encode everything into typestate that you can . Preserve codebase quality . This is a complex distributed system, so implement carefully.

Run cargo check, cargo clippy (treat warnings seriously), and cargo test proactively and often. Before completing each bead, run the relevant cargo check/clippy/tests for the touched crates/modules. Run the full test suite at the end of each phase.

After each of these, I would want to run /new so that I can queue up the next prompt, and leave codex running without me having to go outside of codex and script it .

Additional information

_No response_

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗