Desktop Console

See the nodes deployed to your team and inspect their runs from your Mac or Windows computer. Execution happens on the managed service; Console displays it locally.

ATFGraph Console run timeline, spans and inspector

Example run inspection: the screenshot follows the docs theme. These are recorded multi-step runs, not the hello-world result. Your hosted Console uses your signed-in team and environment.

The Homebrew cask and standard installers include Console. On macOS it is installed at ~/Applications/ATFGraph Console.app.

Console needs the CLI session on this same computer. If it is open, quit it first. Then:

atfg login
atfg whoami
open "$HOME/Applications/ATFGraph Console.app"

For Homebrew with an older CLI on PATH, use "$(brew --prefix)/opt/atfgraph/bin/atfg" login instead. On Windows, open ATFGraph Console from the Start menu after signing in.

Allow access to your saved ATFGraph session if macOS prompts for Keychain access. This is the session's access/refresh token pair. You do not need to paste a graph-server API key into Console.

Pick your team and environment

Choose your team and dev in the header. The signed-in user's permissions determine what is available. A Linux container or VM login does not create the host app's session.

Find a deployed node

Open Agents and find the node label and capabilities. Compare with:

atfg --env dev status hello-world

A local build or newly registered node is not proof that a worker is deployed. Check the deployment result and environment.

Inspect a real run

atfg --env dev run hello-world.greet '{"name":"Ada"}'

Open Runs, find the returned run ID and inspect its status, input, output and path. A deterministic greeting may have no model token usage or cost.

Understand usage and costs

Open Costs to compare recorded model usage by node, model and capability over the selected time window. Unpriced calls are counted separately; the displayed total is not necessarily the total provider bill. A deterministic hello-world run has no model usage to populate these panels.

Open Observability to follow a run's trace, event log and available metadata. Use the run ID to connect these views to the execution you submitted.

ATFGraph Console: Costs in light mode and Observability in dark mode

Light mode shows the Costs example; dark mode shows the supplied Observability trace and event log. Screenshots show example instances and data, not usage from this walkthrough.

Quit Console, run atfg login on the host, and reopen it. If teams still fail to load, check atfg whoami and atfg doctor. An unavailable service cannot be fixed by reinstalling the app.

macOS first launch

Current builds are not notarized by Apple. If macOS blocks the app you just downloaded, use its per-app Open Anyway control in Privacy & Security. Homebrew does not bypass Gatekeeper.

Current scope

Use Console for deployed nodes and run inspection. Some advanced administrative views can show unavailable routes; platform tokens, server settings and identity administration are outside the first-node walkthrough. Those messages are not a request to supply your own server admin key.