Skip to content

Feature Request: Customizable Agent target for ⌘+Enter (launch Claude Code / OpenCode / other CLI agents instead of built-in Agent) #9651

@Kayphoon

Description

@Kayphoon

Pre-submit Checks

  • I have searched Warp feature requests and there are no duplicates
  • I have checked the known issues page

Feature Description

Currently, ⌘+Enter (or Ctrl+Enter on Windows/Linux) always opens Warp's built-in Agent mode. I'd like the ability to customize what ⌘+Enter launches — specifically, to map it to an external CLI agent like OpenCode, Claude Code, Gemini CLI, or any user-specified command.

Use Case

I use multiple AI coding agents throughout my day:

  • OpenCode for codebase-aware tasks
  • Claude Code for extended reasoning
  • Warp Agent for quick terminal questions

Right now, switching between them requires manually opening a new tab and running the command. If I could configure ⌘+Enter to launch my preferred agent (or choose between them), it would eliminate a constant context-switch friction.

Proposed Solution

Add a setting under Settings → AI → Agent Mode (or similar):

Default Agent Target (dropdown):

  • Warp Agent (current default)
  • Claude Code
  • OpenCode
  • Custom command... (text input field)

When set to "Custom command", the user can enter any CLI command (e.g., opencode, claude, gemini), and ⌘+Enter will open a new pane/tab running that command instead of Warp's built-in Agent input.

Why This Matters

  • Many developers are now using multiple AI agents for different strengths
  • CLI agents like OpenCode and Claude Code are becoming primary workflows
  • Having a single, consistent "launch my agent" shortcut across tools reduces cognitive load
  • This also addresses the keybinding conflict in changing the agent mode keybinding from ⌘⏎ for long-running commands (e.g. claude) #8989 — if the user can remap ⌘+Enter to their preferred tool, the conflict disappears naturally

Alternatives Considered

  1. Disable Warp Agent entirely — works (per changing the agent mode keybinding from ⌘⏎ for long-running commands (e.g. claude) #8989 workaround) but loses all AI features
  2. Use a shell alias — doesn't integrate with Warp's pane/tab system
  3. Custom keybinding to run a command — Warp doesn't currently support "run arbitrary command on keybinding"

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:settings-keybindingsSettings UI, preferences, keybindings, and keyboard-shortcut management.area:terminal-inputTerminal command-line input, cursor movement, key handling, and input editing.enhancementNew feature or request.needs-mocksrepro:highThe report includes enough evidence that the issue appears highly reproducible.triagedIssue has received an initial automated triage pass.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions