Bug reportCompleted

Ctrl+I shortcut for Agent Input does not work across agent CLI terminals

Đạt Trần WPCPosted

Bug Details

Location: Project > Terminal > Agent Input shortcut

Description:
The Agent Input field shows Ctrl+I as the shortcut, but the shortcut does not appear to work when using different agent CLI terminals in 1DevTool.

I tested this with multiple agent CLIs, including Claude, Codex, and Cline. In these terminals, pressing Ctrl+I does not focus or activate the Agent Input field as suggested by the UI.

There is also a conflict/ambiguity with Cline: inside Cline, Ctrl+I is already used for switching between Plan and Act mode. Because of this, the same shortcut cannot reliably be used for Agent Input in Cline sessions.

Actual:
- The UI displays Ctrl+I as the Agent Input shortcut.
- Pressing Ctrl+I does not activate Agent Input in Claude, Codex, or Cline terminals.
- In Cline, Ctrl+I is already used for Plan/Act mode switching, creating a shortcut conflict.

Expected:
- The shortcut displayed in the Agent Input field should work consistently across supported agent CLI terminals.
- If Ctrl+I is reserved or intercepted by a specific CLI such as Cline, 1DevTool should avoid using it there or provide a configurable alternative shortcut.
- The UI should only show a shortcut that is actually available and functional in the current terminal context.

Impact:
This makes the Agent Input shortcut misleading and reduces keyboard-only usability. Users may repeatedly try the displayed shortcut without any response, and Cline users may experience confusion because the same key combination is associated with Plan/Act switching instead of focusing Agent Input.

Attachment:
Screenshot attached showing the Agent Input field displaying the Ctrl+I shortcut.12:53 AM

Reproducibility: Unknown · Impact: Minor issue

Environment

VERSION
unknown
OS
ARCH
CHANNEL

Attachments

  • userjot-flcj1iivl49m91ky7fk2goc6.png

    userjot-flcj1iivl49m91ky7fk2goc6.png · 111 KB

Resolution progress

  1. PENDING

  2. REVIEWING

  3. IN PROGRESS

  4. COMPLETED

Discussion0

Newest first
  • No comments yet. Add context or ask a question below.

Sign in to comment, vote and follow this request.

Sign in to reply