Summary
When selecting a workspace in loom tui, there should be actions to open a shell or editor in that workspace — mirroring loom shell and the proposed loom editor command (see related issue).
Motivation
loom shell is available from the CLI but not from the TUI. Since the TUI is the interactive way to manage workspaces, it's a natural place to offer quick actions like opening a shell or editor for the selected workspace. Currently you have to exit the TUI and run loom shell <name> separately.
Commands affected
Modules affected
Proposed behavior
When a workspace is selected in the TUI, offer keybindings to:
- Open a shell in the workspace (equivalent to
loom shell)
- Open the workspace in the configured editor (equivalent to
loom editor, once that feature exists)
Acceptance criteria
Summary
When selecting a workspace in
loom tui, there should be actions to open a shell or editor in that workspace — mirroringloom shelland the proposedloom editorcommand (see related issue).Motivation
loom shellis available from the CLI but not from the TUI. Since the TUI is the interactive way to manage workspaces, it's a natural place to offer quick actions like opening a shell or editor for the selected workspace. Currently you have to exit the TUI and runloom shell <name>separately.Commands affected
loom initloom newloom addloom removeloom downloom listloom statusloom execloom shellloom saveloom openloom registryModules affected
tuiworkspaceconfigProposed behavior
When a workspace is selected in the TUI, offer keybindings to:
loom shell)loom editor, once that feature exists)Acceptance criteria
loom editoris implemented[terminal]and[editor]config as the CLI commands