Tour the AkôFlow interface
AkôFlow Desktop is the visual client for the AkôFlow daemon. The application does not run infrastructure commands from the browser renderer: it requests the daemon API, and the daemon performs discovery, planning, execution, data movement, and infrastructure operations.
A current Desktop overview. The numbered markers identify the navigation and status controls; counts and workflow names change with the selected instance. Open a workflow row or select View all to continue into a record.
- The sidebar groups workflows, infrastructure, runs, artifacts, provenance, and audit.
- Global search opens entities without first visiting their list page.
- Notifications report operations that need attention.
- The instance indicator confirms which daemon the client is using.
Main areas
| Area | What you do there | Main API domain |
|---|---|---|
| Overview | Check registered environments, workflows, and completed runs | Multiple read endpoints |
| Workflows | Create versioned definitions and inspect activity DAGs | /workflow-definitions/ |
| Planning sessions | compare algorithms and promote a candidate to a plan | /planning-sessions/ |
| Infrastructure | Connect environments, discover resources, and define execution scopes | /environments/, /resources/, /execution-scopes/ |
| Runs | Start and inspect workflow, standalone, simulated, and interactive runs | /execution-runs/ |
| Artifacts | Register, build, locate, and materialize executable artifacts | /artifacts/, /artifact-builds/ |
| Provenance | Query evidence and follow lineage | /provenance/ |
| Audit | Inspect the operational event history | /audit-events/ |
Follow the ownership hierarchy
AkôFlow pages preserve the relationship between records. An execution belongs to a plan, a plan belongs to a workflow, and a provisioning operation belongs to a cloud resource. Breadcrumbs show that chain; their ancestors are links.
For example:
Use the back control below the breadcrumb to return to the logical parent. Its destination remains correct even when the page was opened from search or a notification.
Desktop and API are two views of the same operation
Most task guides contain two paths:
- AkôFlow Desktop explains the controls, validation, progress, and resulting detail page.
- API shows the corresponding HTTP request and a minimal payload.
The API path is useful for automation and reproducible experiments. The Desktop path is useful for exploration, comparison, and live monitoring. Records created through either path appear in the same interface.
Use global search deliberately
Press ⌘+K on macOS, Ctrl+K on Windows or Linux, or select the search field in the title bar. With an empty field, Desktop lists navigation shortcuts such as Workflow definitions, Planning sessions, Runs, and Provenance. This is the fastest route when you know the product area but not its sidebar location.
Once you enter text, the list changes to matching control-plane entities. A result identifies its record by title and ID, and may show a status and type; select it to open the corresponding record. Press Enter to open the first available result, or Escape to close the result list.
Search is a locator, not an investigation surface. It does not replace the filtered lists or the provenance query tools: use the workflow, run, plan, environment, or provenance page after opening a result when you need status history, evidence, or a precise server-side filter. If Desktop says Search is temporarily unavailable, the search request failed; retry after confirming that the daemon connection is healthy.
Global terminal
Interactive commands open in the terminal panel fixed to the bottom of the application. The daemon owns the session and streams its output; closing a page does not make the renderer execute or manage a remote shell itself.
Open an interactive session from a resource or runtime-aware operation, then use the terminal panel to inspect its output. The session detail page provides the durable record and log-export control; the panel is a live view, not a replacement for the persisted session evidence. See Interactive console for prerequisites, connection behavior, and recovery.
Read-only instances
Some instance modes prevent write operations. The interface displays the active mode and guards creation, update, execution, and destructive actions. Read-only exploration, provenance, and audit remain available according to the daemon configuration.
Continue
Start with your first end-to-end run, or connect execution infrastructure.