Feature Reference

Keybindings, refresh semantics, shortcut scope and launch details for ait trails

Keybindings

Every key below can be rebound — press ? for the in-place editor, or open Settings → Shortcuts. See Shortcut scope for how a rebind here relates to the board.

KeyActionContext
sOpen the trail selector — re-scans the project for trails firstAny time; the selector also opens on launch
rRe-read task files from disk and redraw the loaded trailTrail selected
dFetch the active trail again from storage and re-check its freshnessTrail selected
ROpen the agent workflow that re-authors the active trailTrail selected; not while a launch is already starting
vOpen the trail’s summary in a scrollable dialogThe trail has a summary
TOpen the /aitask-trail creation workflow for the focused task — the workflow confirms before it writesFocused live local card (a ghost card, or no focus, gives a warning)
EnterOpen the focused member’s detail screenFocused card
Up / Down / Left / RightMove between cards and waves
jTUI switcher
?Shortcut editor
qQuit

In the detail screen

KeyAction
aReveal the whole trail document, or return to the focused member’s own material
EscapeClose the detail screen

What each refresh reads

KeyTask filesStored trailList of trails
rRe-readNot read — the loaded copy is redrawnNot read
d—Fetched again, then freshness re-checkedNot read
s——Re-scanned
R—A new version is written by the agent after you confirm; the view reloads it when it lands—

None of r, d and s writes anything. For the costs of each key and the drift reasons a card can show, see By-Trail in the board reference — the view is the same.

Not available here

These keys belong to the board’s By-Trail view and do nothing in ait trails:

KeyBoard actionWhy not here
mMove the focused entry’s task to a columnThere are no board columns in this TUI
MMove the focused wave’s tasks to a columnSame — use the board (how-to)
SSync task data with the remote, then redrawSync from the board or with ait sync, then refresh here

Shortcut scope

The trail keys are the board’s own shortcuts: ait trails registers under the board scope and uses the same bindings, so an override such as

shortcuts:
  board:
    trail_select: o

in aitasks/metadata/userconfig.yaml rebinds the key in both ait trails and the board’s By-Trail view.

The ? editor inside ait trails lists the board rows this TUI uses — the trail keys, navigation and quit — plus the shared actions. To rebind a key that only the Kanban board uses, open the editor from ait board or use Settings → Shortcuts.

Launch and environment

LaunchNotes
ait trailsFrom a shell in the project
j → iFrom any TUI, through the TUI switcher; i is not shown on the switcher’s hint row, but the entry is listed
  • Task directory — read from TASK_DIR (default aitasks).
  • Read-only — the TUI never writes a trail, a task, or board_config.json; a project without a board configuration file is left without one.
  • Separate selection — the trail shown here is independent of the trail the board’s By-Trail view shows; switching TUIs does not carry it across.