collin/browser-terminal-extension
5114c62f5e29cb906a7d816a11e9da773ae34940 / TODO.md
| 1 | - [ ] be able to talk to claude about anything on the page |
| 2 | - [ ] remote host tmux session |
| 3 | - [ ] Idea: pull off a tab out side of the browser and it puts it within your default terminal emulator |
| 4 | - [ ] TODO: get working well on unconfigured tmux |
| 5 | - [ ] TODO: investigate chrome wterm and vercel wterm |
| 6 | - [x] Idea: pinned tab / session mode |
| 7 | - right-click a session or window tab to pin it to the browser tab you are |
| 8 | on, by site or by that exact tab; localhost ports are matched to sessions |
| 9 | by devport's hash when nothing is pinned. See README, "Pinning a session |
| 10 | to a browser tab". |
| 11 | - the same pins read backwards too: moving the terminal activates the tab |
| 12 | pinned to where it landed. Own checkbox, "and switch tabs back". |
| 13 | - [ ] send to claude should auto name window using llm |
| 14 | - [ ] typing cd in omnibar should have a ui for selecting dir |
| 15 | - this will change the directory of the current tmux session |
| 16 | - [ ] I notice that ctrl-shift-l focuses our omni bar properly when used within our extension, but when the page is focused, using ctrl-shift-l doesn't properly select the text in our omnibar |
| 17 | - we kinda got it working with a werid workaround hack which closes then re-opens |
| 18 | - this is okay, but janky |
| 19 | |
| 20 | - [ ] does neovim have a way to probe the terminal's background color |
| 21 | - [ ] use claude in chrome with a browser on a different machine |