Features

Paneflow is a native, GPU-accelerated workspace for running CLI coding agents in parallel. It is not a hosted agent runtime or a generic terminal feature checklist. It gives you visible panes, project context, agent state, local orchestration, and review surfaces around the tools you already run.

New to Paneflow? Start with Get started, then use this page as the feature map.

Feature map

• Workspace: panes, layouts, projects, tabs, and session restore. Read Layouts.
• Agents: agent panes, project threads, free chats, and lifecycle status. Read Conductor.
• Context: file tree, branch badges, dev-server ports, and clickable URLs. Read Shortcuts and actions.
• Orchestration: CLI, JSON-RPC IPC, paneflow up, paneflow flow, and event streams. Read Scripting.
• MCP: read-only pane access for configured agents. Read Scripting.
• Review: Git worktrees, diff columns, review prompts, and human-approved handoff. Read Review.
• Settings: themes, terminal defaults, workspace templates, and AI access controls. Read Settings.

Workspace model

Paneflow has two core layers: workspaces and panes. A workspace is an independent project context. A pane is a real terminal split inside that workspace.

Split the focused pane horizontally (Cmd/Ctrl+Shift+D) or vertically (Cmd/Ctrl+Shift+E). Each new pane starts a shell in the same working directory. Move focus with Alt+Arrow, open another workspace with Cmd/Ctrl+Shift+N, and reshape the current pane tree with the four layout presets: even horizontal, even vertical, main vertical, and tiled.

Session restore saves the workspace layout, pane tree, working directories, custom buttons, projects, and chats. Terminal scrollback stays process-local, so a relaunched workspace starts with fresh terminal output. Paneflow does not keep child processes alive after the app has closed, so restart long-running dev servers or agents when the underlying process exited.

Agent supervision

Launch Claude Code, Codex, OpenCode, Gemini, Pi, Hermes, or any CLI agent that is available on your PATH. Paneflow runs the agent in a normal PTY pane, so you can watch the raw terminal, interrupt it, or take over with the keyboard.

Supported and hooked agents can report richer lifecycle state such as thinking, waiting, finished, errored, or stalled. Other CLI tools still run in panes, but Paneflow may only know what it can infer from the process tree and terminal activity.

Inside a project, use project threads for independent agent sessions scoped to the codebase. For research, planning, or quick questions outside a project, open an agent chat from your home directory (~). Past chats stay reachable from the sidebar.

Workspace context

Point Paneflow at a codebase and it becomes a project: the file tree opens in the sidebar, the active Git branch is visible in the header, and new panes are scoped to that directory. Open several projects as tabs in one window when you need to move between repositories without losing each pane's local context.

The file tree lets you browse the current workspace, open a file next to an agent session, and copy absolute or relative paths for prompts and commands. Custom action buttons let you pin frequent commands such as build, test, lint, or dev-server starts to the top of the window.

When a process inside a pane binds a listening port, Paneflow attributes the port to that pane from the OS process and socket tables on Linux, macOS, and Windows. Known frontend tools such as Next.js, Vite, Nuxt, Remix, Astro, Webpack, Angular, and React scripts can surface clickable URLs. Terminal banner matching adds labels for more server types when output contains enough signal.

Scripting and MCP

The paneflow binary is also a local CLI over Paneflow's JSON-RPC IPC socket. Scripts can list panes, read scrollback, search output, inspect agent state, stream lifecycle events, split panes, focus panes, prefill prompts behind a write gate, spawn declarative workspaces with paneflow up, and run multi-agent DAGs with paneflow flow.

Paneflow also ships a read-only MCP bridge. Once installed for a supported agent, it exposes list_panes, read_pane, and search_pane so an assistant can inspect another pane without copy-paste. The bridge cannot type into panes or control them, and terminal output is returned as untrusted data.

The full command reference lives in Scripting and automation.

Worktrees and review

Create Git worktrees for independent tasks without touching your main checkout. Paneflow opens each worktree as its own context with its own branch, files, panes, and agent sessions. This makes parallel agent work visible without collapsing every task into the same working tree.

The review surface shows worktree diffs side by side with hunk navigation, review prompts, and embedded review terminals. Paneflow can prefill prompts for an agent, but the normal flow stays human-approved: you decide what gets sent and when it is submitted.

Read the Review page for the full workflow.

Keep exploring

• Shortcuts and actions - the default keymap and action names for paneflow.json overrides.
• Configuration - where paneflow.json lives and what every key does.
• Troubleshooting - Vulkan on Linux, Gatekeeper on macOS, DirectX on Windows, PATH, fonts.