Use case
I'm using opcode as part of an automated PBI (Product Backlog Item) workflow. When I start a work session, a shell script:
- Creates a LiteLLM virtual key for cost tracking
- Finds the relevant PBI markdown file
- Should open opcode with the correct project and the PBI content pre-loaded as context
Currently there's no way to do this without manual interaction.
Request
Please add one of the following (in order of preference):
Option A – URL scheme
opcode://open?path=/Users/me/projects/kira&prompt=<encoded_text>
Option B – CLI arguments
/Applications/opcode.app/Contents/MacOS/opcode --path /Users/me/projects/kira --prompt "..."
Option C – Launch file (.opcode.json)
A file format that opcode recognizes on open, containing project path + initial prompt.
Current workaround
Copying the PBI content to clipboard via pbcopy and asking the user to manually paste after launch. Works, but breaks the automation flow.
Environment
Use case
I'm using opcode as part of an automated PBI (Product Backlog Item) workflow. When I start a work session, a shell script:
Currently there's no way to do this without manual interaction.
Request
Please add one of the following (in order of preference):
Option A – URL scheme
Option B – CLI arguments
/Applications/opcode.app/Contents/MacOS/opcode --path /Users/me/projects/kira --prompt "..."Option C – Launch file (
.opcode.json)A file format that opcode recognizes on open, containing project path + initial prompt.
Current workaround
Copying the PBI content to clipboard via
pbcopyand asking the user to manually paste after launch. Works, but breaks the automation flow.Environment