Navigation

There are three ways to get around: the icon-band panels, the sidebar tree, and the command palette.

Panels

The icon band on the far left switches the sidebar between five panels, in this order:

PanelShortcutShows
SchemaAlt+1APIs, resources, operations, request instances, middlewares
EnvironmentAlt+2Environments and the variable schema
WorkflowsAlt+3Workflows, their scripts, and the run screen
OpenAPIAlt+4The spec itself, effective or as imported
HistoryAlt+5Past request executions and workflow runs

Only one panel is visible at a time; the icon band is how you swap. Toggle the sidebar itself with Ctrl+B; the choice persists across restarts.

Each panel in turn:

  • Schema: the project tree, and the main way around. Detail below.
  • Environment: the variable schema (which variables exist, their type, whether they're required or secret) and one entry per environment for the values. The extends chain is shown as nesting, so an environment sits under the one it extends. See environments.
  • Workflows: every workflow in the project, with its scripts underneath. Create, rename, duplicate, and delete from here. The panel's home screen is the run screen, where you pick workflows, bind an environment per API, fill inputs, and run.
  • OpenAPI: the spec as a document, filterable, with a toggle between the effective spec (what API Craft actually uses, your overrides applied) and the source spec exactly as imported. Selecting an operation elsewhere can jump you straight to it here.
  • History: every past run, requests and workflows on separate tabs. See History.

The schema tree

The Schema panel is the main way to navigate. It nests:

API
├── Resource
│   └── Operation
│       └── Request instance
└── Middlewares

Click an item to open it in the main content area: an operation opens its request view, a resource or API opens its overview. Opening an operation loads its temp request if one exists.

The command palette

Press Ctrl+K to open the command palette and jump directly to any API, resource, operation, or saved request, or switch environments and run actions, by typing. It's usually the fastest way to move in a large project.

Going back

Every place you open goes on a navigation stack, whichever way you got there: a click in a tree, the command palette, a link in a doc, "show in spec", a history entry, a workflow run. Alt+← goes back through it and Alt+→ forward, like the Back/Forward of an IDE. Both are also in the command palette as Back and Forward.

The stack works across panels: going back from a request can land you on an environment, a workflow, or a spec operation. Opening something new after going back drops the forward part. Items that were renamed are followed under their new name; items that were deleted are skipped.

The breadcrumb

The request view shows a breadcrumb (API › Resource › Operation › Request) so you always know where you are. It's a location indicator, not a control.

There's no tab strip: one thing is open at a time, and the navigation stack is how you get back to the previous one.