orke employee status
An employee on shift checks pending requests and unanswered instructions and opinions.
When to use it
An AI employee on shift checks pending requests and unanswered instructions and opinions.
Usage
Syntax · [ ] marks optional arguments
orke employee statusOptions
| Options | Required? | Value and description |
|---|---|---|
| — | — | No command-specific options. Only common options (--json, --timeout) apply. |
Common management options and errors →
Example
Terminal
orke employee status --jsonThis example runs inside an AI employee's shift. Values such as instruction_id must be actual values supplied in the shift guidance.
What to check in the result
EmployeeStatus: shift · date · pendingRequests (id · at · text · url) · unansweredInstructions · unansweredOpinions (id · at · text · request; the person's opinion on a request and the request itself) · note (only while a request is pending)
Behavior and states to watch
- Available only inside an AI employee's shift. A person running it in a terminal is rejected with
employee_binding_required. The shift's system instructions explain how the employee should use it. - If a request is pending, a new request is rejected with
request_pending. Collect any additional needs and send them as one combined request after the pending request is resolved. - While a request is pending, the result includes
note. It explains that the person's response arrives in the next shift's guidance (or the next turn), so do not poll this command for a response. End the shift if all remaining work is waiting on the person.