Using Gestalt Mobile

Choose a workspace

The Sessions tab presents a recursive filesystem tree rooted at --cwd. Directories containing .git are terminal nodes. Directory symlinks are shown only when their real targets remain inside the root; cycles and duplicate real targets are omitted.

Keyboard controls follow tree conventions: Left/Right collapse or expand, Up/Down move, Home/End jump, and Enter or Space select.

The Sessions tree stops at repository boundaries and keeps the selected working directory visible.

Start and reopen sessions

At startup, Mobile asks Codex app-server for available models. New sessions use gpt-5.6-terra by default unless you choose another discovered model. Durable threads are resumed after a relay restart.

Use Open for a released, stopped, or attention-required session. If a Codex upgrade removed the saved rollout, Mobile can bind a replacement thread while preserving the relay session and settings; it reports that earlier Codex history is unavailable.

Session policy is explicit before Codex starts; Chat stays disabled until a session is ready.

Skill profiles

Global profiles live in ~/.gestalt/skill-profiles/<name>.yml:

version: 1
name: focused
skills:
  - name: typescript-advanced-types
    path: /absolute/path/to/SKILL.md
    enabled: true

gestalt mobile --skills list
gestalt mobile --cwd "$PWD" --skills focused

An explicit global profile wins over a workspace gestalt-skills.yml, which wins over Codex-native selection. Mobile never rewrites Codex configuration or skill files. Skills provided by the Gestalt plugin are always shown and advertised to new sessions; they are labeled Always advertised and cannot be disabled by a saved snapshot. When Agents is upgraded, refresh the editor catalog and start a new session to use the new version.

Save complete skill selections as named profiles for repeatable sessions.

Chat and approvals

Chat restores the canonical Codex thread timeline and follows live output. It keeps command approvals, file-change approvals, and bounded questions beside the turn that requested them. Pending interactions remain durable across a browser reload.

Prompts, commentary, final answers, timing, and relay readiness stay together.

File approvals name every target before the user accepts or denies the write.

Supervised plans

The Plan tab belongs to the selected session. It presents ordered milestones, nested steps, the current action, skill assignments, progress, and review status. Completing implementation does not hide the distinction between work that is awaiting review and work whose evidence has been accepted.

The Sessions view reports a server-derived Working or Idle verdict. Working requires an active root or child, an owned process, or a verified Autopilot continuation. Idle includes completed work, manual Off, a request for your attention, and the important degraded state: an incomplete plan without a continuation. Time passing alone never makes work look active.

Autopilot labels are exact: On · root working, On · continuation scheduled, On · waiting for agent event, On · checking state, Paused · needs you, Safety paused, On · continuation unavailable, Off, and Complete. On · continuation unavailable means an incomplete plan has no verified next action, so it is degraded rather than healthy waiting. “On” records requested intent; the controller-health detail proves whether the next action is actually observable. If it says incomplete without a continuation, run gestalt doctor, then use gestalt update and restart Mobile when doctor reports unavailable or incompatible supervision capabilities.

The active milestone stays readable while nested work advances.

Review status remains explicit after implementation reaches done.

Prompt recovery

A composer draft stays in session-scoped storage until its matching relay operation is accepted. If sending is interrupted, rejected, or its outcome is unknown, return to that session and retry the exact text; it is not copied into status evidence, telemetry, or diagnostics. An accepted operation clears only the submitted revision, so newer text remains in the composer.

Git operations

The Git tab has an independent filesystem selection. It shows branch divergence, dirty counts, recent commits, and allowed repository actions.

• Pull uses git pull --rebase.
• Push is offered only for an upstream branch that is ahead and not behind.
• Mobile never creates an upstream and never force-pushes.
• Clone targets must be ordinary directories, not existing repositories.

The Git tab separates repository inspection from the Sessions workspace selection.

Scratchpad

Scratchpad is a browser-local note surface reached from configuration. Notes persist without becoming prompts or modifying the repository.

Keep temporary context close without adding it to the Codex thread.