Search and notifications

Global search is backed by the Engine catalogs. Notifications are a Desktop convenience built by tracking operations and polling their existing APIs; there is no notification collection endpoint.

Search from Desktop

1. Focus Search AkôFlow in the top bar, press /, or press ⌘K/Ctrl+K.
2. Enter an ID, name, state or other indexed value.
3. Select a result, or press Enter to open the first result.
4. Press Escape to close search.

With an empty query, the field filters quick navigation destinations. A non-empty query waits 220 ms, queries the Engine and shows entity results. Each result includes a direct interface path, so selecting it opens the corresponding detail or filtered list page.

Search covers:

Type	Representative indexed values
workflow	ID, external ID, name, namespace
execution	ID, title, resource/runtime IDs, failure and status
artifact	ID, name and version
environment	ID, name, description and status
resource	ID, name, provider, region, zone and type
plan	ID, algorithm, objective, workflow version and scope
scope	ID, name, topology and environment versions
materialization	ID, variant, digest, resource, run, activity, path and status

The Engine ranks an exact field match above a prefix match, which ranks above a substring match. Results with equal score preserve catalog order.

Search through the API

export AKOFLOW_URL='http://127.0.0.1:<daemon-port>/akoflow-api'
export AKOFLOW_TOKEN='<daemon-token>'

curl --get --fail-with-body \
  -H "Authorization: Bearer $AKOFLOW_TOKEN" \
  --data-urlencode 'q=science' \
  --data-urlencode 'types=workflow,execution,artifact' \
  --data-urlencode 'limit=20' \
  "$AKOFLOW_URL/search/"

The response shape is:

{
  "query": "science",
  "results": [
    {
      "type": "workflow",
      "id": "science-workflow",
      "title": "Science workflow",
      "subtitle": "default",
      "path": "/workflows/science-workflow",
      "score": 0.9
    }
  ],
  "total": 1
}

limit defaults to 30 and is capped at 100. Omit types to search every supported type. Unknown type names are ignored; if every supplied name is unknown, the result is empty. An empty q returns an empty result without loading catalogs. A catalog failure returns 500 Internal Server Error.

Follow operation notifications

The bell in the top bar reports completed or terminal states for operations started in this Desktop profile:

• planning sessions;
• executions;
• artifact builds;
• interactive terminals;
• cloud provisioning;
• Desktop application updates.

Select an operation notification to mark it read and open its associated page. Use the check control to mark all current items read. The center retains at most 40 entries.

Tracked operations are polled every five seconds. A notification is created when a tracked operation reaches completed, failed, cancelled, closed, ready, or destroyed, depending on its type. A terminal disappears from the active-session list when closed, which completes its tracked notification.

Profile-local state

Notification entries and the list of tracked operations live in browser local storage. They are not audit or provenance records, do not synchronize between Desktop profiles, and may disappear when site data is cleared. Use Audit, execution details, planning details, or build details for durable operational evidence.

Native operating-system notifications are emitted only when the browser/renderer exposes the Notification API and permission has already been granted. The current interface does not prompt for notification permission.

API equivalents

There is no /notifications/ endpoint. Automation should query the resource that owns the operation:

# Planning session
curl -H "Authorization: Bearer $AKOFLOW_TOKEN" \
  "$AKOFLOW_URL/planning-sessions/$PLANNING_SESSION_ID/"

# Execution run
curl -H "Authorization: Bearer $AKOFLOW_TOKEN" \
  "$AKOFLOW_URL/execution-runs/$RUN_ID/"

# Active interactive sessions
curl -H "Authorization: Bearer $AKOFLOW_TOKEN" \
  "$AKOFLOW_URL/console-sessions/"

# Provisioned cloud instances for one environment
curl -H "Authorization: Bearer $AKOFLOW_TOKEN" \
  "$AKOFLOW_URL/environments/$ENVIRONMENT_ID/cloud-instances/"

For a durable cross-domain timeline, query /audit-events/ with the appropriate execution, session, connection, resource or environment filter.

When results do not appear

• Wait until at least one non-whitespace character is entered; an empty server query deliberately returns no entities.
• Search only returns records visible through the same catalogs as their list pages.
• A red error message means the Engine request failed; verify the API token and daemon, then retry.
• Notifications only cover operations started and tracked by the current Desktop profile. Opening the app after an operation was started elsewhere does not reconstruct a notification history.