Hello, recently discovered this tool.
It fits almost perfectly into what I'm looking for, minus subshells.
Would you be open to a configuration option that has the following effect:
treehouse get allocates a new worktree and prints the path to stdout (no subshell)
treehouse return <dir> returns it back to the pool
treehouse without arguments requires a command
(implicit get unexpected behavior when there's a return expected afterwards)
Reasoning: I want to ask a subagent to work in a pooled worktree and just inspect the branch afterwards.
Hello, recently discovered this tool.
It fits almost perfectly into what I'm looking for, minus subshells.
Would you be open to a configuration option that has the following effect:
treehouse getallocates a new worktree and prints the path to stdout (no subshell)treehouse return <dir>returns it back to the pooltreehousewithout arguments requires a command(implicit
getunexpected behavior when there's areturnexpected afterwards)Reasoning: I want to ask a subagent to work in a pooled worktree and just inspect the branch afterwards.