Run Independent Background Prompt Sessions in the Hermes CLI

Use /background <prompt>—also available as /bg or /btw—when a self-contained task can run beside the foreground conversation. Hermes starts a separate agent session instead of adding a hidden branch to the current history.

Know what is inherited

A background prompt inherits the active model, provider, toolsets, reasoning settings, and fallback model. It does not inherit the foreground conversation history. Include every file path, constraint, expected output, and verification requirement the task needs.

Several numbered background tasks can run concurrently while the foreground stays interactive. Their results appear in terminal panels and use standalone task IDs; they do not become messages in the main conversation history.

Launch checklist

Make the prompt self-contained.
Use absolute paths when the working location matters.
State whether the task is read-only or may edit files.
Define the exact deliverable and verification gate.
Avoid parallel edits to the same files.
Record task IDs for later inspection.

Common pitfalls

Referring to “the file we discussed.” The background session cannot see foreground history.
Confusing background prompts with delegated subagents. They are separate standalone sessions with their own result panels.
Running conflicting writers. Isolation does not merge simultaneous file edits safely.
Assuming panel output entered the main transcript. Bring verified findings back explicitly when needed.

Verification

Start a read-only background prompt that reports a harmless file fact. Continue chatting in the foreground, then confirm the result appears under its task ID and did not alter the foreground history. For write tasks, inspect the artifact and rerun its tests before accepting the panel's summary.

Official references: Hermes CLI guide and slash commands.