A complete guide to the Agent Panel
The Pekan documentation now has a dedicated Agent Panel guide for anyone starting or steering a conversational coding session. It walks through installing the Codex ACP or Claude Agent ACP adapter, opening a project-scoped session, choosing read-only or write access, and deciding between reviewing each request and automatic approval. A compact comparison explains when to use the Agent Panel, an Agent Action, or a Workspace terminal, so the differences in interaction, repeatability, and worktree behavior are clear before work begins.
The guide follows the whole session lifecycle: attaching task context, understanding the working badge, sending files and messages, answering access prompts and questions, queueing editable follow-ups, stopping a turn, switching through project session history, closing, resuming, and reviewing file or Git changes. It also documents the exact approval boundary, including the important warning that a linked project directory is not an operating-system sandbox for the adapter process or its own tools.
Privacy and troubleshooting sections explain what prompts, task context, attachments, project content, and board tools can reach the selected local adapter or provider. They also cover missing adapters, failed starts, projects without a linked directory, non-Git folders, unavailable board tools, refused access, disconnected sessions, and provider-gated commands. The in-app Help page now links directly to this guide, and the related setup, views, and Agent Actions pages point to it without duplicating the full instructions.
Highlights
- A task-based Agent Panel guide covering setup, sessions, access, approvals, task context, queues, history, diffs, privacy, and troubleshooting.
- A compact comparison of Agent Panel sessions, Agent Actions, and Workspace terminal launches.
- Concrete safety examples distinguish Pekan-mediated scope checks from full operating-system isolation.
- In-app Help and related website documentation now link directly to the guide.