Workspaces and terminals#

A workspace binds a PacketBench layout to one local or remote project root. Each terminal pane is a real PTY session; commands run as your user on the selected machine.

Before you start#

• The project path exists and is readable.
• The selected shell or coding CLI is installed.
• For repository features, the project is a Git checkout.

Create and arrange a workspace#

1. Open the project directory.
2. Add Terminal panes for the shells or CLIs you need.
3. Split or move panes to create the working layout.
4. Check each pane's project and host label before running commands.
5. Close unused sessions rather than leaving background processes attached.

Workspace layouts persist, but restored panes are dormant until opened. This prevents an application restart from silently launching commands.

Delegate from a workspace#

Use Delegate when you want an agent conversation scoped to the same project. Review the target path, provider and permission posture in the launcher. A remote workspace remains remote when delegated; do not assume a similarly named local checkout is the target.

Verify#

Run these checks in a new pane:

git rev-parse --show-toplevel
git status --short

The reported top level must match the workspace path. On a remote pane, also run hostname and confirm it is the configured server. Stop if any identity is unexpected.

Terminal history and application metadata may persist separately from the project. See Data, security and upgrades before copying or deleting PacketBench state.

If it does not work#