What Fynvra is, and how the window is laid out
Fynvra is a local multi-agent coding workbench. You talk to one orchestrator; it splits the request into tasks, hands each to its own worker, then reviews and merges. This page maps the real window so you know where everything is and what to click next.
The window at a glance
Section titled “The window at a glance”The title bar sits on top: the left sidebar toggle on one side, Settings, theme, and the right panel on the other. Settings covers the window; press Esc or use the close button to return. Below it the window splits into three areas.
Left
Workspaces → sessions
Section titled “Workspaces → sessions”Use + next to “Workspaces” to attach a folder. The chevron expands sessions for each workspace; a session row shows a status dot, role badge, and relative time.
Center
Chat and file tabs
Section titled “Chat and file tabs”The tab strip always includes “Chat”. Opened files, terminals, and diffs add tabs. A chat runs from title, messages, and approval bar down to the composer and status bar.
Right
Files / Tasks / Changes
Section titled “Files / Tasks / Changes”The Tasks tab shows the number of tasks in the current run. Drag the panel’s left edge to resize it, or double-click to restore the default width.
On first launch there is no workspace yet: the center shows only “Attach folder”, and the right panel asks you to pick a workspace. Attach a folder first, then create a session.
Five terms
Section titled “Five terms”-
Workspace
A folder you attach. A Git repository is orchestrated with a separate worktree per task; a plain folder shows “No git” and runs in place.
-
Session
A conversation with one role. Status is idle, running, waiting for approval, or error. Session records stay on this computer.
-
Orchestrator
The built-in main agent. It plans, dispatches, reviews, and merges, and by default does not edit code. New sessions select it by default.
-
Worker
An agent given one task. It edits in its own Git worktree and reports back; without Git it edits the attached folder in place.
-
Inbox
Messages between a worker and the orchestrator: questions, replies, instructions, and done reports. The task details show the stream; an idle orchestrator wakes when a new message arrives.
Where to go next
Section titled “Where to go next”If you have not installed yet, start with Install. If the app is already open, follow Quick start to connect a model, attach a folder, and send the first request.