Skip to content

feat: add per-agent custom CLI arguments via agentArgs setting#53

Open
sscotth wants to merge 1 commit intostandardagents:mainfrom
sscotth:feat/agent-custom-args
Open

feat: add per-agent custom CLI arguments via agentArgs setting#53
sscotth wants to merge 1 commit intostandardagents:mainfrom
sscotth:feat/agent-custom-args

Conversation

@sscotth
Copy link

@sscotth sscotth commented Mar 11, 2026

Summary

  • Adds a new agentArgs setting to .dmux.global.json (and per-project .dmux/settings.json) that allows specifying custom CLI arguments per agent
  • Custom arguments are appended to agent commands across all launch paths: initial prompt, no-prompt, resume, conflict resolution, and attach-agent
  • Includes input validation and 9 new tests covering all prompt transport types

Example config

{
  "agentArgs": {
    "gemini": "--model gemini-3.1-pro-preview",
    "claude": "--model sonnet"
  }
}

Motivation

Some agents don't default to the desired model. For example, gemini CLI doesn't show gemini-3.1-pro-preview by default, so --model gemini-3.1-pro-preview needs to be passed manually. This setting automates that across all dmux launch flows.

Test plan

  • tsc --noEmit passes
  • All 34 tests pass (9 new tests for custom args across positional, option, stdin, send-keys transports, and resume commands)
  • Manual: set agentArgs in ~/.dmux.global.json and verify args appear in launched agent commands

Allow users to specify custom CLI arguments for specific agents in
.dmux.global.json or .dmux/settings.json (e.g. {"agentArgs": {"gemini":
"--model gemini-3.1-pro-preview"}}). Arguments are appended to agent
commands across all launch paths including initial prompt, resume, and
conflict resolution.
@sscotth sscotth force-pushed the feat/agent-custom-args branch 3 times, most recently from 01cdd52 to 7d8a93a Compare March 11, 2026 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant