neovim nvim embedded terminal support request

[robcmills]

I tried to run opencode inside a neovim embedded terminal buffer. Results were not great.

• whole layout severely broken
• header appeared to be off-screen above
• every other line appeared to be blank, maybe some kind of text wrapping bug
• I could not focus the primary prompt input correctly, insert mode was putting characters into the buffer below the input

[Hippo0o]

setting the theme to system seems to fix this issue for me.

[kbnopro]

I encountered the same issue, but not as severe.
When trying to run opencode in floating terminal (toggleterm.nvim), the layout seems to be shifted up a bit:

After some investication and comparison with lazygit (which works correctly), it seems that the bottom bar is overflowing because opencode read the width of the current app, not the terminal itself.

[nickjvandyke]

setting the theme to system seems to fix this issue for me.

Initially this didn't work for me, but after upgrading to v0.3.5, it looks correct so far! Other themes still get messy but not a big deal.

[adamdotdevin]

i think someone was working on an opencode.nvim plugin, too, which will be another solution

[nickjvandyke]

@adamdotdevin that might be me haha https://github.com/NickvanDyke/opencode.nvim

It's affected by this bug, unless I'm missing some way to work around it.

Related, it'd be helpful to expose a --theme CLI option so I can default to 'system' in the plugin rather than instruct users to manually modify their opencode config 😀

[adamdotdevin]

@adamdotdevin that might be me haha https://github.com/NickvanDyke/opencode.nvim

It's affected by this bug, unless I'm missing some way to work around it.

Related, it'd be helpful to expose a --theme CLI option so I can default to 'system' in the plugin rather than instruct users to manually modify their opencode config 😀

will add this flag

[kbnopro]

Just want to let you guys know the new version 0.3.5 is now working for me when setting theme to system

[nickjvandyke]

oops, I just noticed there is also https://github.com/sudo-tee/opencode.nvim - did not mean to steal any thunder 😀

It seems to work around this limitation by making its own UI over opencode run

[geekmdtravis]

I was having the same issue. Using ghostty, on macOS, with Neovim running the TokyoNight theme.

I can confirm that the problem resolves by setting the theme to system, which is a reasonable workaround for now.

[nickjvandyke]

will add this flag

I just migrated https://github.com/NickvanDyke/opencode.nvim to call opencode's server API rather than send text to the necessarily embedded TUI, so --theme is now much lower priority from my perspective 🙂

[robcmills]

Update:

Thanks to Hippo0o for suggesting switching to system theme which did improve things for me.

However, it appears I am unable to scroll back/up to see the full session output?

Maybe this is a personal config issue? Any ideas?

[nickjvandyke]

@robcmills it looks like you're in Normal mode - you have to be in Terminal mode (Insert mode, essentially) to send inputs like scrolling to the TUI

[robcmills]

@NickvanDyke thanks for responding. I see. I guess this is a result of fundamental design/architecture decisions with regard to the TUI.

I was comparing it to Claude Code, which appears to just output to stdout in the terminal, sequentially appending. Whereas Opencode is rendering "fullscreen" and scrolling has to be accomplished through opencode, by sending keybindings that do not conflict with the environment, whether that is the parent terminal itself, or in this case neovim. Is this an accurate assessment?

This is somewhat disappointing to me, because the primary reason I use embedded terminal buffers in neovim is so that I can hit escape to switch to normal mode, and navigate terminal output the same way I navigate normal buffer contents, with all the same keybindings I am accustomed to in neovim, e.g. gg to go to start of session, G to go to bottom, navigating to specific lines, marks, etc.

I wonder if this is something worth accommodating for in opencode? Or am I just ignorant of the justifications for these choices?

Maybe offer some sort of configuration layout option, that is either "fullscreen" (current layout) or "append" (more like Claude Code, in that output is just appended to stdout)?

That could be one way to address/workaround this issue, as well as a whole class of other TUI layout bugs...