Skip to content

openers config: allow extra CLI args for the claude (and other attach-dirs) opener, e.g. --dangerously-skip-permissions #1347

Description

@ChampPABA

What I'm trying to do

Use openspec workset open <name> --tool claude to launch a Claude Code
session with several repos attached (--dir per member), so an agent
working on a cross-repo feature (spec lives in a planning store, code lives
in several separate component repos) can see and edit all of them in one
session.

What's missing

The documented openers schema (docs/cli.md) only supports two fields
per tool:

{
  "openers": {
    "zed": { "style": "workspace-file" },
    "claude": { "attach_flag": "--dir" }
  }
}

There's no way to pass additional static CLI flags to the launched binary.
Concretely, I want workset open to launch Claude Code with
--dangerously-skip-permissions (and potentially other flags in the
future), but the attach_flag field only controls the per-member
attachment flag, not extra one-time flags for the tool itself.

Proposed fix

Add an optional field, e.g. extra_args: string[], to the attach-dirs
opener shape:

{
  "openers": {
    "claude": {
      "attach_flag": "--dir",
      "extra_args": ["--dangerously-skip-permissions"]
    }
  }
}

workset open would append extra_args to the launch command after the
--dir <member> flags.

Workaround I'm using today

Not using workset open for this case — copying the member paths from
openspec workset list and launching manually:

claude --dangerously-skip-permissions \
  --dir <store> --dir <repo-a> --dir <repo-b>

Works fine, just loses the one-command convenience workset open is meant
to provide.

Version: @fission-ai/openspec@1.5.0 (checked schema against v1.6.0
release notes/docs too — same openers shape as of that release)

Related: #1257 describes the same multi-repo store setup (one planning
store, several component repos) that led me here — different ask (docs
example vs. this config gap), but same underlying use case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions