Feature Summary

Allow users to customize CLI execution commands for each provider through Settings > Connections. This enables full control over how agent CLIs are invoked, including custom flags, arguments, and execution parameters.

Problem or Use Case

Currently, CLI execution flags are hardcoded in the provider registry. Users cannot:

• Use codex --yolo instead of --full-auto (see [feat]: use --yolo for codex #659)
• Add provider-specific flags like --search, --enable collab
• Customize resume flags, default arguments, or initial prompt handling
• Use custom CLI paths or wrapper scripts

This limitation forces users to accept default behavior that may not fit their workflow or security preferences.

Proposed Solution

Add a settings modal accessible via a gear icon (⚙️) next to each detected provider in Settings > Connections. The modal provides granular control over:

Key features:

• Real-time command preview showing the final assembled command
• Shell-style argument parsing (supports quoted strings: --message "hello world")
• Reset to defaults button
• Settings persist across sessions

Implementation

I have a working implementation ready:

Changes:

• src/main/settings.ts - Storage and CRUD for custom configs
• src/main/ipc/connectionsIpc.ts - IPC handlers
• src/main/services/ptyManager.ts - Shell-style arg parser + config application
• src/renderer/components/CustomCommandModal.tsx - Settings UI
• src/renderer/components/CliProvidersList.tsx - Settings button integration

PR: Will link after this issue is created.

Related Issues

• [feat]: use --yolo for codex #659 - [feat]: use --yolo for codex
• Various requests for custom CLI flags and execution parameters

Additional Context

This is a generic solution that addresses multiple feature requests by giving users full control over CLI invocation, rather than adding individual flags one by one.