Navigate the work Herdr already owns.

Understand the hierarchy, discover existing project directories, and follow the layout as it adapts from phones to wider displays.

Open the user guide

The navigation model

Server Session Space Agents Agent page

Server: the saved SSH endpoint.
Session: a named, persistent Herdr namespace.
Space: a project container associated with a working directory.
Agents: named agent conversations within the space.
Agent page: status, bounded output, response controls, and selected chat.

Select and manage sessions

Opening a Herdr server shows its session lobby. Select a running session to open its work. A preferred session is optional; leaving it blank uses the last-used or Herdr-declared default.

New session requires a valid unused name and explicit Create & start confirmation. A running non-default session can be stopped after confirmation, then removed separately only after discovery verifies it stopped. Session rename is unavailable in Herdr 0.9.0.

Choose an existing directory for a space

A space associates Herdr work with an existing remote working directory. HerdRanger’s SFTP folder picker can browse and select that directory. Creating a space does not create the project directory itself.

A server’s optional Default projects folder controls where discovery and the folder picker begin. It is a device-local setting and does not move existing spaces or project files.

Open automatically discovered projects

For the configured projects folder, HerdRanger reads up to 200 immediate, visible child directories over SFTP. Discovery does not recurse, follow symbolic links, run shell commands, or modify the server.

Selecting a discovered project follows one of three paths in the running default session:

If an agent already uses that exact directory, HerdRanger opens its existing space and agent.
If a matching space exists without an agent, HerdRanger starts the configured default agent in that space.
Otherwise, HerdRanger verifies that the directory already exists, creates a space for it, and starts the configured default agent.

Project discovery never creates a new project directory. It only opens work associated with a directory that already exists, and it never starts a different session.

Adaptive navigation and dual-pane chat

Navigation adapts to available width. On narrow displays it appears below the conversation; on wider displays it appears on the left. When enough width is available, HerdRanger automatically uses a dual-pane presentation with navigation beside the selected conversation. The divider can be adjusted.

Pinned agents appear above the status sections. Other agents are grouped as Blocked, Working, Done, Idle, or Unknown so status is conveyed by text as well as color.

Understand agent identification

HerdRanger can label common configured kinds including Codex, Claude, Gemini, Pi, OpenCode, Copilot, Grok, Local AI, and a title-cased custom kind. New-agent choices can include Codex, Claude, Gemini, Pi, OpenCode, Copilot, and a configured local kind.

These labels identify configuration; they are not a claim that every provider is installed, authenticated, or compatible on every host. The selected kind must already be configured through Herdr on the host. HerdRanger does not install provider tools, perform provider login, or collect provider tokens.

If launch is rejected: authenticate or install the provider through its official workflow on the host, refresh HerdRanger, and try once more. HerdRanger does not retry an ambiguous launch automatically.

Treat mutations as remote operations

Creating, renaming, closing, deleting, or moving work changes authoritative Herdr state. Confirm the named target. If the network result is ambiguous, inspect the remote state before repeating the action.

Confirmed agent or space removals may queue behind a running operation. HerdRanger revalidates each target before closing it. A failed or unconfirmed operation stops the remaining queue; rename, move, and create actions are never queued.