Workspace control

The Workspace tab operates Herdr's topology on a host — the same workspaces, tabs, and panes you'd manage at the desk. (For how the hierarchy fits together, see sessions & workspaces.)

Pick a host

Select the machine to operate at the top. The tab shows that host's current topology, refreshed live from the bridge; pull to refresh forces a new snapshot.

What you can do

• Create a workspace — give it a working directory (an absolute path on the host, e.g. /home/you/code/myproject) and an optional label. This is how you spin up a fresh project context before starting an agent in it from the terminal.
• Create and close tabs inside a workspace.
• Split and close panes inside a tab.

Destructive operations — closing tabs and panes — always go through a confirmation sheet naming exactly what will close. Commands are live-only and expire within seconds if not delivered, so a flaky connection produces visible failures rather than delayed surprises.

Boundaries in the current beta

• Directory paths are typed, not browsed — there's no remote file picker yet.
• Closing a whole workspace, renaming things, and choosing split direction/ratio aren't exposed in the app yet.
• Hosts advertise what they support (host capabilities); operations a host can't perform are unavailable rather than silently failing.

Typical flow

1. Create a workspace rooted at your project.
2. Open its pane in the terminal.
3. Start your agent there (claude, codex, …) as you would locally.
4. Steer it from the session cockpit once it appears on Signal.