orke employee action
Record published posts, comments, and messages.
When to use it
Record a post, comment, or message immediately after publishing it. Counts appear as “Posts 1 · Comments 3” in the journal and “Today: Posts 2 · Comments 5” in the UI, helping the person review the employee's work. There is no count limit.
Usage
Syntax · [ ] marks optional arguments
orke employee action --kind <post|comment|message> --url <string> [--note <string>] [--key <string>]Options
| Options | Required? | Value and description |
|---|---|---|
--kind | Required | post | comment | messageType of item published. |
--url | Required | URL of the published post or comment. |
--note | Optional | One-line note. |
--key | Optional | Key for an action that may be sent again. Within a shift, the same key identifies one record. |
Common management options and errors →
Example
Terminal
orke employee action --kind post --url "https://example.com/posts/123" --note "Introduction post" --key post-1 --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
{kind, today, duplicate?} — today is today's recorded count for that kind. It is informational and does not prevent further posts.
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 you send the same action again within a shift using the same
--key, it is not recorded again, andduplicate: trueis returned. - UI and journal counts are recorded by the employee. Check actual actions in the UI's ledger as well.