Shortcuts reference
The keyboard shortcuts shown on screen, and where to find the REST and command-line references for each kind of task.
Use a shortcut only on the surface that currently shows it. This page does not define CLI commands. A keyboard action never widens permission, approves paid work, or proves that an external action completed.
Your agent keeps its goal, context, model, local edits, native builds and tests, and final decisions. The five Work tools are lithi.quote, lithi.run, lithi.batch, lithi.status, and lithi.result. Reporting uses a separate reporting:read API or approved report file; it is not a shortcut or a sixth Work tool.
Read shortcuts from the current surface
Keyboard behavior depends on focus, the active view, and whether an input or modal owns the key event. When a remembered shortcut and the current screen disagree, use the visible control.
An old screenshot, copied shortcut list, or another Lithi surface is not a keyboard contract for the page in front of you. A shortcut can invoke only an action already available on that surface; it does not bypass review or authorization.
If a keyboard action does nothing, use the visible control and report its current label, route, and visible state. Keep private content and credentials out of support notes.
Use REST from a terminal
For HTTP guidance, use REST from a terminal. For executable terminal syntax, follow the references supplied with your approved client. This page does not define that command surface.
Do not infer a terminal command from an MCP tool name. lithi.status, lithi.result, lithi.quote, lithi.run, and lithi.batch are MCP work tools, not lithi status, lithi result, lithi quote, lithi run, or lithi batch CLI commands.
Likewise, a local CLI parse is not proof that a remote operation succeeded. Keep a CLI error or result separate from account, job, delivery, and payment state.
Keep local checks scoped
A local readiness indicator proves only the check it names. It does not establish authentication, account targeting, provider availability, completed Compute work, or payment.
When you need bounded verification guidance, use Test Lab. When you need terminal guidance, use REST from a terminal.