Sessions and terminals

Start work, follow its progress, and reopen it later.

User guideEnglish

Sessions and windows are different

A session is a running shell or AI task. A terminal window is the view where you watch and interact with it. Closing a window keeps a live session running. You can clear your screen while a long task runs, then return to the same work.

Start a new task

  1. In “New session,” choose a recognizable name, such as “Update homepage menu.”
  2. Choose a shell or AI and the environment where it will run.
  3. Select a working folder and start.
  4. Read the terminal’s startup screen and any errors, and complete any required sign-in.
  5. Send the task and how you want the result checked. In a regular shell, enter commands.
A specific promptRead the README in this folder and summarize the installation process in five steps. Show me the summary before changing any files.
orke showing the status of multiple AI sessions in one view

Read task status

SituationWhat to do next
WorkingRead the progress output and results, and wait.
Waiting for input or approvalOpen that terminal, read the request, and respond.
Completed or process exitedCheck the final response, files, and test results.
Exit status needs checkingUse “Check termination again” in the task list.

Close, reopen, or end

ActionResult
Close a terminal window or tabCloses the view and keeps the running session.
Open from the task listReconnects to the same live session.
End a sessionRequests that the actual task end.
Quit orke entirelyAlso ends running sessions. Live work is not restored after restarting the PC.

On Windows and Mac, the app window’s × hides the app view. Closing a web window or web tab inside the workspace closes that page. Closing a terminal window and closing a web page have different effects.

Copy, paste, and interrupt

On Windows, Ctrl+C copies when text is selected and interrupts when it is not, following the two-press rule. Use Ctrl+Shift+C to always copy, and Ctrl+V to paste. On Mac, use ⌘C and ⌘V; Ctrl+C interrupts.

When sharing an error with an AI, include the output and the command that produced it.

Manage sessions with commands

Use session commands to read lists, screens, and output, or to create and end sessions. Sessions created through the CLI appear in the list without automatically opening a window. Reading output and entering text are separate actions.

Search documentation

The page could not be displayed. Reload ×