# ZoneGaze Flow Core Features

This guide documents the feature surface that is common to the web UI, direct Mac app, direct Android app runtime, and CLI launch path. The project source is the source of truth; this page summarizes the user-facing behavior and links back to implementation files.

Related docs:

- [Feature coverage matrix](feature-coverage-matrix.md)
- [Feature catalog](feature-catalog.md)
- [Software manual](../manual/software-manual.md)
- [Cline integration](cline-integration.md)
- [Runtime API reference](../reference/runtime-api.md)

## Workflow Evidence

The core workflow recording shows the real web UI sequence used for this documentation pass: board input, create-task process, settings/process view, Git/review output, archive result, and the produced demo website result.

Video: [open core working demo](../assets/videos/zonegaze-flow-core-working-demo.webm)

![ZoneGaze Flow core working demo video](../assets/videos/zonegaze-flow-core-working-demo.webm)

Result screenshot: [open produced website result](../assets/screenshots/core-produced-website-result-page.png)

![Produced website output after a ZoneGaze Flow workflow](../assets/screenshots/core-produced-website-result-page.png)

## Project Management

ZoneGaze Flow manages one or more Git workspaces from the project sidebar. Users can add local projects, enter a manual path, use remote browsing, initialize a Git repository, clone a repository, switch active projects, remove projects, and open a workspace in supported local tools.

The UI also has explicit states for no project, disconnected runtime, and blocked access. Project state and metadata are surfaced through the runtime state stream so the board, top bar, Git controls, settings, and detail panels stay synchronized.

Screenshot: [open board input](../assets/screenshots/core-board-input.png)

![Project sidebar and board input state](../assets/screenshots/core-board-input.png)

Source links:

- [Project navigation panel](../../flow/web/src/components/project-navigation-panel.tsx)
- [Runtime API reference](../reference/runtime-api.md)

## Board And Work Items

The canonical board lanes are Plan Later, Plan Review, Backlog, Next Up, In Progress, Review, Done, and Archive. The runtime still stores the Done lane using the historical `trash` id, but the user-facing title is Done. Archive, deleted, and removed areas are visible from the board controls.

Work items support title, prompt, tags, filters, sort order, lane moves, restore, archive, delete, remove, generated child prompts, task images, file mentions, base refs, agent overrides, model/provider overrides, reasoning overrides, plan mode, work type, parent task, and auto-review choices.

Screenshot: [open archive result](../assets/screenshots/core-archive-result.png)

![Archive output state after using board controls](../assets/screenshots/core-archive-result.png)

Source links:

- [Board columns contract](../../flow/contracts/src/api-contract.ts)
- [Kanban board UI](../../flow/web/src/components/kanban-board.tsx)

## Task Inputs

The create-task flow accepts the user prompt, optional child prompts, images, file mentions, parent task, work type, target agent, base ref, plan mode, model settings, and auto-commit or PR behavior. Pasted multi-line lists can be split into multiple cards.

Screenshot: [open create-task process](../assets/screenshots/core-create-task-process.png)

![Create task dialog showing prompt, work type, parent, base ref, plan mode, and agent settings](../assets/screenshots/core-create-task-process.png)

Source links:

- [Task create dialog](../../flow/web/src/components/task-create-dialog.tsx)
- [Task CLI command](../../flow/runtime/src/commands/task.ts)

## Work Types And Hierarchy

Default work types are Epic, Story, Task, and Subtask. Epic and Story are coordinator types; Task and Subtask are executable types. Subtask requires a parent. Allowed parent rules default to Story under Epic, Task under Story, and Subtask under Task.

Settings let users enable, disable, color, label, icon, and validate work types. Workflow flags control hierarchy use, parent status cascade, planning hierarchy mode, coordinator validation, auto-create and launch, auto-pick next, concurrent descendant start, parallel planning, and parallel implementation.

Source links:

- [Work type contract](../../flow/contracts/src/work-types.ts)
- [Work type settings section](../../flow/web/src/components/work-type-settings-section.tsx)
- [Configuration reference](../reference/configuration.md#board-and-workflow-flags)

## Dependencies And Chained Work

Tasks can be linked so one task blocks another. The board can show blocked and ready work, and task start logic can choose eligible descendants or linked work when workflow flags allow chained execution.

How-to steps: [create linked tasks](../user/how-to.md#create-linked-tasks)

Source links:

- [Dependency linking hook](../../flow/web/src/components/dependencies/use-dependency-linking.ts)
- [Task start/link logic](../../flow/runtime/src/commands/task.ts)

## Home Agent And Planning

The ZoneGaze Flow Agent entry in the sidebar is the home/planning agent surface. It can help create or edit tasks, link tasks, split plans into cards, and preserve a planning session. Coordinator-generated tasks can land in Plan Review before being published to Backlog.

Screenshot: [open agent sidebar](../assets/screenshots/agent-sidebar.png)

![Agent sidebar with project and ZoneGaze Flow Agent entry](../assets/screenshots/agent-sidebar.png)

## Agents

The catalog knows about Cline, Claude Code, OpenAI Codex, Factory Droid, Kiro, OpenCode, and Gemini. Launch support is intentionally narrower than catalog support. Native Cline appears to users as ZoneGaze Flow and runs through the local Cline SDK boundary; CLI agents run through PTY-backed sessions.

Native Cline/ZoneGaze Flow supports provider and model selection, custom provider base URLs and headers, API key or OAuth/device auth, account metadata, reasoning effort low/medium/high/xhigh, Plan/Act behavior, slash commands, `/clear`, prompt history, file mentions, image attachments, queued messages, persisted chat, resume, cancel/abort, tool labels, token snapshots, and context recovery where the SDK supports it.

Source links:

- [Agent catalog](../../flow/runtime/src/core/agent-catalog.ts)
- [Cline SDK boundary](../../flow/runtime/src/cline-sdk)
- [Cline integration guide](cline-integration.md)

## Terminal And Shortcuts

The runtime uses PTY-backed sessions for CLI agents and workspace shell commands. The web UI exposes a persistent terminal panel that can reconnect, resize, clear, stop, restore, expand, minimize, and mirror session output. Shortcut commands are configured in settings and run through the workspace shell.

Screenshot: [open terminal panel](../assets/screenshots/terminal-panel.png)

![Terminal panel attached below the board](../assets/screenshots/terminal-panel.png)

Source links:

- [Persistent terminal manager](../../flow/web/src/terminal/persistent-terminal-manager.ts)
- [PTY-backed CLI agents ADR](../adr/0005-pty-backed-cli-agents.md)

## Review And Shipping

The detail view combines chat or terminal output, task children, latest activity, warnings, progress, file tree, column context, working-copy diff, last-turn diff, binary file handling, unified and split views, syntax rendering, collapsible blocks, line/range comments, send-comments-to-agent, commit prompts, PR prompts, auto-review cancellation, and move-to-Done actions.

Screenshot: [open Git and review output](../assets/screenshots/core-git-output.png)

![Git and review output surface](../assets/screenshots/core-git-output.png)

## Git And Worktrees

Git features include current branch, upstream divergence, changed file count, additions/deletions, fetch, pull, push, checkout, refs, commit list, commit search, commit diff, working-copy diff, task worktree diff, and explicit discard actions where supported.

Task execution normally uses isolated worktrees. The runtime can ensure and delete task worktrees, label paths, track metadata, detect detached or head state, and show changed files with additions and deletions.

Screenshot: [open Git history](../assets/screenshots/git-history.png)

![Git history view with refs, commits, and diff](../assets/screenshots/git-history.png)

## Settings Context Access Updates And PWA

Settings sections cover General, ZoneGaze Flow/Cline, Work Types, Git Prompts, Notifications, Appearance, Project Context, and Project. General settings select the default agent and autonomous mode. Git prompts can reset commit and PR templates. Appearance covers preview and layout reset. Notifications cover browser notification permission and app behavior.

Project context settings cover user profile, project memory, context files, retention windows, automatic updates, dynamic retrieval, conversation pruning, in-context compaction, procedural memory, zero-context subagents, tool schema optimization, governance, architecture notes, testing guidelines, and skill suggestions.

Access features include local/remote host binding, passcode enforcement, in-memory sessions, rate limiting, internal CLI bearer token propagation, PWA support, update notification, and Featurebase feedback when the selected agent account is authenticated enough to request a token.

Screenshot: [open settings process](../assets/screenshots/core-settings-process.png)

![Settings surface showing core configuration areas](../assets/screenshots/core-settings-process.png)

Source links:

- [Runtime settings dialog](../../flow/web/src/components/runtime-settings-dialog.tsx)
- [Passcode manager](../../flow/runtime/src/security/passcode-manager.ts)
- [Featurebase feedback button](../../flow/web/src/components/featurebase-feedback-button.tsx)
- [Configuration reference](../reference/configuration.md)

