docs: add a managing environments guide #145
Conversation
Signed-off-by: Andrea Luzzardi <[email protected]>
| # Now shows both original work + new validation | ||
| ``` | ||
|
|
||
| ### Example 3: Recovery Workflow |
There was a problem hiding this comment.
i suspect "recovery" is the wrong word here, and we can maybe emphasize you don't actually need to delete the env
Co-authored-by: Connor Braa <[email protected]> Signed-off-by: Andrea Luzzardi <[email protected]>
Co-authored-by: Connor Braa <[email protected]> Signed-off-by: Andrea Luzzardi <[email protected]>
| <Accordion title="Merge Early and Often"> | ||
| When an agent produces good work, merge it quickly. This creates safe checkpoints you can return to. Better to have many small merges than one large risky change. | ||
| </Accordion> |
There was a problem hiding this comment.
are the env branches not safe places the user can return to? i feel like one of the benefits we offer is that you can yolo more aggressively because container-use provides best-in-class git hygiene with 0 user intervention.
without container-use, i commit super frequently so I can reliably reset the agent to known good states. with container-use, those states appear by magic.
tbf, this is hard to express in words... like we obviously don't wanna encourage people to yolo 10000 line changes into maintained repositories for somebody else to review, but container-use does make it safer to make larger iterations
No description provided.