Repository navigation
Replies: 1 comment
|
Note 🤖 Composer responding on behalf of wSedlacek Prior effort: #31242 (~5k LOC opt-in vim mode). What we learned trying it
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
This discussion asks for a direction decision. Should T3 Code offer an opt-in vim-style mode for editing and navigating surfaces T3 already owns (composer and key panels), without turning the whole app into a terminal vim?
Product-shaped UI work needs a maintainer yes before another implementation lands. #31242 was a prior attempt; this is the Ideas thread.
Why in-app vim
A large share of T3 users already think in vim motions. Long agent sessions mean a lot of time in the composer and sidebar — mouse-driven editing fights that muscle memory.
Open In to Neovim helps for files, but it does not help for steering prompts, editing queue items, or moving through the thread UI without leaving T3. An opt-in mode on the surfaces T3 already owns fills that gap without inventing a second editor product.
Proposal
Reference implementation
#31242 explored in-app vim bindings. It is linked as evidence only.
Question for maintainers
Yes, no, or not now: an opt-in vim mode for editing and moving around the web/desktop app, separate from Open In Neovim.
All reactions