Skip to content

Feature Request: URL scheme or CLI arguments for programmatic launch #458

@michi-rechberger

Description

@michi-rechberger

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:

  1. Creates a LiteLLM virtual key for cost tracking
  2. Finds the relevant PBI markdown file
  3. 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

  • opcode v0.2.0, macOS

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions