Skip to content
Eddy

Using Eddy

Eddy is built to be driven from the keyboard, and everything has a mouse path too. This page covers the keys, the palette, lists, the dependency graph, logs and threads. Press ? in the app at any time for the same key list.

Full reference: web/src/lib/keys.ts (the key registry) in the repository.

Keyboard map

Letters work when no text field has focus. A two-key sequence such as g f means press the keys one after the other, within a second. j and k also answer to the down and up arrows, l to Enter and the right arrow, and h to Escape and the left arrow. On Windows and Linux the palette is Ctrl K.

Move around

  • jMove down
  • kMove up
  • lOpen selected
  • hGo back up
  • ggJump to top
  • GJump to bottom
  • uJump to owner
  • [Previous page in this nav group
  • ]Next page in this nav group

Go to

  • gfFleet overview
  • gtThreads
  • gkAccess tokens
  • gaMy audit log

Find and ask

  • ⌘KSearch every cluster
  • :Commands only
  • /Filter this list
  • aAsk AI about the selection
  • dDetails panel
  • ?Keyboard shortcuts

Clusters

  • 1…9Switch to cluster 1 to 9
  • {Previous cluster
  • }Next cluster
  • nAdd a cluster (fleet page)

Act on the selection

  • rReconcile
  • RReconcile with source
  • sSuspend or resume
  • LLogs (pods and workloads)
  • oOverview tab
  • eEvents tab
  • yYAML tab
  • tThreads tab
  • cNew thread (on the Threads tab)

In logs

  • fToggle follow

In the graph

  • 0Fit the graph to the screen
  • +Zoom in
  • -Zoom out
  • FFocus on the selected node and its neighbours (again: whole graph)

The command palette

Press ⌘ K to search resources and commands.

  • Scope. Inside a cluster, the palette searches that cluster, and it is instant. Press Tab (or use the scope toggle) to widen it to every cluster. On the fleet page it already searches every cluster. Matches rank by fuzzy name, then failing resources first.
  • Commands. Type : first to show commands only. They depend on what is selected: reconcile, suspend or resume, show logs, jump to the owner, ask AI, new thread, go to a page of resources, pin a cluster, toggle the theme and open the key list.
  • Clusters. Clusters appear as Switch to … commands. Outside the palette, 1 to 9 switch to that cluster directly, and { and } go to the previous and next one.
  • Needs attention. With an empty query the palette lists what needs attention first.

Lists, filters and status

  • The sidebar groups kinds by project (Flux and the presets you enabled). Each list shows a status pill per row: Ready, Failed, Reconciling, Suspended, Unknown or Completed. Lists sort what needs attention first.
  • Press / to filter the list you are looking at. j and k move, l opens, h goes back.
  • Cluster colours and environments (set by the operator) tint each cluster, so a production cluster is hard to mistake for staging. Rows update live, with a short flash when a status changes.
  • Objects a Kustomization applied that Eddy does not watch appear as inventory-only rows: their kind, namespace and name, never their content.

Reconcile, suspend and resume

Select a Flux resource and press r to reconcile, R to reconcile with its source first, or s to suspend or resume it. These run as you, so they need patch in that cluster (see Access and RBAC). On a protected cluster you type the cluster name to confirm.

The dependency graph

A Kustomization or HelmRelease has a Manages section with three views:

  • Tree: the ownership tree of what it created.
  • Graph: dependencies, sources and managed objects, live. Edges show first → then ordering, the source, what a resource applies, and what is waiting.
  • Outline: the same graph as a list, step by step.

Arrow keys, h j k l and Enter move along the edges while the graph has focus. Open a group node (double-click or Enter) to expand it. Press F to focus on a node and its neighbours, 0 to fit the graph, and use + and - to zoom. The right-click menu offers reconcile, focus and open.

Logs, YAML and events

  • Tabs on a resource: o Overview, y YAML, e Events, t Threads, and L Logs for pods and workloads.
  • YAML and events are read as you, so you see them only if your RBAC allows. YAML is redacted, Secret YAML is never shown, and ConfigMap data is stripped.
  • Logs stream only while you are viewing them. A workload log (Deployment, StatefulSet, DaemonSet or Job) follows several pods at once. Press f to toggle follow. You need get on pods/log.

Ask AI on a selection

When an operator has enabled it (see Ask AI), select a resource and press a to ask about it. Press a again to go back to Details. You can attach selected log lines or a YAML excerpt to a question. Answers can be wrong, so check them before acting, and commands in them are copy-only.

Threads

Threads are review conversations on a resource or a cluster. Open the Threads tab (t) and press c to start one. Threads from Claude Code carry a via mcp badge. An Ask AI answer can be saved as a thread. g t lists all the threads on resources you can see, and you can reply or resolve them there.