orke employee start
Enable work. The first shift starts immediately.
When to use it
Same as “Start work” in the UI. The first shift starts immediately; later shifts follow the schedule and working hours in the work settings.
Usage
Syntax · [ ] marks optional arguments
orke employee start --slug <string>Options
| Options | Required? | Value and description |
|---|---|---|
--slug | Required | Employee identifier (slug) returned by employee list. It may differ from the displayed name. |
Common management options and errors →
Example
Terminal
orke employee start --slug employee_slug --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
EmployeeWork: slug · changed · phase · running
Behavior and states to watch
- If work is already enabled, no action is taken and
changed: falseis returned. Starting again does not add another shift. - If there is no goal, or a problem with the settings or work AI, the response includes
employee_start_refusedand the reason, without changing state. - Shifts run only while orke is running, including in the system tray.
- This is a human (operator) command. Calls from an AI employee on shift are rejected with
control_forbidden.