Cursor Positioning Bug in Agent Description Input

Resolved 💬 4 comments Opened Aug 11, 2025 by plx Closed Jan 6, 2026

Bug Description
When entering the description for a new agent, the cursor always jumps to the end of the current text, which makes it impossible to "go back and edit" within the TUI; I work around via copy-and-paste, but it's very clunky and very specific to that screen—no other component has the same behavior.

To illustrate the issue, let's say I wrote this:

Hello strange bugX

...(with the X the current cursor position). If I moved it here:

Hello strangeXbug

...and then hit backspace, here's the result:

Hello strang bugX

Which means:

  • the intended operation got applied to the cursor location
  • the cursor location got "reset" to the end of the content

This bug has been consistent for me since the first release with the /agents command available, and only manifests on that one screen.

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 1.0.72
  • Feedback ID:

Errors

[{"error":"AxiosError: Request failed with status code 403\n    at XN (file:///Users/prb/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:682:1077)\n    at Unzip.K0 (file:///Users/prb/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:683:9955)\n    at Unzip.emit (node:events:519:35)\n    at Unzip.emit (node:domain:489:12)\n    at endReadableNT (node:internal/streams/readable:1696:12)\n    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n    at EB1.request (file:///Users/prb/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:685:2088)\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async QH8 (file:///Users/prb/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:2298:470)\n    at async Promise.all (index 0)\n    at async file:///Users/prb/.npm-global/lib/node_modules/@anthropic-ai/claude-code/cli.js:2284:19497","timestamp":"2025-08-11T16:47:21.557Z"}]

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗