orke package author
Open an authoring AI session to build the workflow. The same package and AI continue the same conversation.
When to use it
Open an authoring AI session to build the workflow. The same package and AI continue the same conversation.
Usage
Syntax · [ ] marks optional arguments
orke package author --slug <string> --provider <claude|codex|nvidia|antigravity> [--goal <string>] [--editing <boolean>]Options
| Options | Required? | Value and description |
|---|---|---|
--slug | Required | Package identifier returned by list or create. |
--provider | Required | claude | codex | nvidia | antigravityProvider to use. codex appears as ChatGPT in the UI. |
--goal | Optional | Task for the authoring AI, or a specific web task goal for page.run. |
--editing | Optional | Whether to edit an existing workflow. |
Common management options and errors →
Example
Terminal
orke package author --slug package_slug --provider claudeReplace the example IDs, folders, references, and revision with values from actual queries. Element references such as e7 must also come from the latest observation.
What to check in the result
PackageAuthorDescriptor: slug/sessionId/provider/editing/completedStages
In completedStages, session_reused means an existing running session was returned, while conversation_resumed means a new session resumed the previous conversation.
Behavior and states to watch
- Each package and AI pair has one conversation. If a session for that package and AI is running, it is returned without launching another.
- If no session is running, resume that AI's most recent conversation in the package folder. An AI without resume support (NVIDIA) starts a new conversation.
--editing false(the first authoring session for a new package) always starts a new conversation.- Disconnecting does not end the session.