orke employee journal
Read recent shifts and their work summaries, newest first.
When to use it
Read recent shifts and the “Work done” summary from each. This is the same content as the Journal tab in the UI.
Usage
Syntax · [ ] marks optional arguments
orke employee journal --slug <string> [--limit <integer>]Options
| Options | Required? | Value and description |
|---|---|---|
--slug | Required | Employee identifier (slug) returned by employee list. It may differ from the displayed name. |
--limit | Optional | Number of rows to retrieve. Defaults to 20. Range: 1–200 |
Common management options and errors →
Example
Terminal
orke employee journal --slug employee_slug --limit 5 --jsonReplace employee_slug with the actual slug from employee list, and request_id with an actual id from get or inbox.
What to check in the result
items (newest first): id · reason (first · schedule · now · wake · retry · resume) · result (running · succeeded · failed · interrupted · stopped) · startedAt · endedAt · durationMs · exitCode · failure · provider · model · effort · posts · comments · messages · answer, plus more
Behavior and states to watch
- answer is the shift's original “Work done” text. For shifts that resume the same conversation (Claude and Codex), the text from each continuation is appended in order.
- To see the actual browser actions observed by orke (the ledger), expand “Actual actions” in the UI's journal.
- Shifts started with “Work now” or “Send and work now” have reason now.
- This is a human (operator) command. Calls from an AI employee on shift are rejected with
control_forbidden.