Home/Tutorials/Terminal Overlord

Tutorial 02 · Terminal Overlord

Walk away. Keep the session moving.

Arm HOGSPHERE before launch or during a running Claude Code, Codex, or Grok Build session. It handles supported approval prompts, gives your keyboard priority, and leaves a visible record of every autonomous approval.

About 5 minutesExplicit trust modeSession-scoped log

Arm Overlord and launch in one command

At a normal shell prompt, choose the provider you want to run and add overlord:

codex overlord
claude overlord
grok overlord

PorkiCoder consumes the exact two-word meta-command, confirms that HOGSPHERE is armed, and then launches the allowlisted provider executable. Provider-supported flags can still be used through the separate activation path described below.

The forgotten-permissions use case: if Codex is already deep into a task and you forgot to enable broader permissions at startup, Overlord can supervise the current session. You do not need to kill the agent and lose its working context.

Turn it on during a running session

1

Activate the supervisor

Type the exact command /overlord, press the terminal shield, or use HOGSPHERE's control while a supported provider is in the foreground.

2

Let the agent continue

When a supported approval menu appears, local rules identify the current provider surface and choose a proven affirmative action. One-time or turn-scoped choices are preferred when the provider offers them.

3

Take over whenever you want

Any human keystroke invalidates an in-flight autonomous decision. HOGSPHERE also waits if the terminal foreground changes to a shell, editor, pager, or another process.

The exact /overlord line is recognized only after Enter. Paths, URLs, provider slash commands, and longer prompts containing the word “overlord” continue to the terminal normally.

What HOGSPHERE handles

Deterministic local rules recognize supported command, edit, network, permission, and MCP approval shapes from Claude Code, Codex, and Grok Build. If the same prompt remains after a write, HOGSPHERE can retry after a short acknowledgement window.

Agent questions are left for you. Stale surfaces, secrets, settings, browser completion, payment flows, and ordinary idle composers remain untouched.

HOGSPHERE reads xterm's logical live screen even while you inspect scrollback. Scrollback rows are never evaluated and cannot grant approval authority. If a second approval arrives while the first is settling, PorkiCoder immediately rescans the replacement screen.

Review the log and stop cleanly

Each successful autonomous approval creates a compact speech bubble. Press LOG to open the bounded session history and see the recent actions HOGSPHERE submitted.

Disable Overlord with any of these controls:

  • Type /overlord again.
  • Press the terminal shield.
  • Press HOGSPHERE's STOP button.
  • Exit the provider or close the terminal session.

The approval history is cleared when Overlord stops.

Understand the trust boundary

Overlord is an explicit auto-approval mode. After a screen is proven to be a provider authorization request, its content does not receive an additional risk veto. Broad permissions, destructive commands, production actions, network activity, and MCP tool calls can therefore receive approval.

Enable it for sessions you already trust. The provider sandbox and macOS are the containment boundary. Git can recover many tracked file changes, while external side effects can require separate recovery.

Approval snapshots are evaluated locally and never sent to Gemini or another model. Overlord has no question-answering path or free-text encoder: agent questions always wait for you. Snapshots stay out of chat history.