Use relative path w.r.t cwd for Context.format

[lungsin]

For some models, I got the following error because the model attempts to concatenate the absolute path with the cwd of the opencode:

I'm proposing to use relative path in conjuction with the native opencode file annotation: @<relative path>. So in above screenshot, it would be translated to @lua/klungs/plugins/opencode.lua since my cwd is ~/dotfiles/nvim.

EDIT: After a little bit of testing, it's not enough to just send @<relative path> in the prompt. We also need to specify file/directory attachments. I will investigate the opencode API later.

[nickjvandyke]

We also need to specify file/directory attachments. I will investigate the opencode API later.

opencode.nvim uses the TUI endpoints to leverage opencode's existing UI functionality, and those only support text 🙁 Even the message endpoints don't support explicit file refs. So we are at the mercy of the LLM interpreting the filepaths.

How many models have this issue? I haven't seen it but it seems like a pretty important issue on their end.

Regardless, I have been curious to write the path relative to the server's CWD for conciseness, now that we have that easily available at runtime. Just can't re-use vim.fn.fnamemodify (or whatever it's called) and need to DIY it.

[lungsin]

opencode.nvim already prefers servers that overlap with Neovim's CWD 🙂 See lua/opencode/server/discovery/init.lua

Ah that's good to hear. Thanks for sharing! Now you know that I'm not familiar with opencode.nvim codebase lol 😜

Anw, I found out the issue, it's because of the logic from nodejs used by opencode. Basically they use path.isAbsolute which apparently doesn't consider ~/<path> as absolute. Hence, it gets concatenated further with cwd. So, I think the quick fix for us is to expand ~ to $HOME (maybe there's a neovim API for this, I'm not sure).

Refs:

• My debugging session with opencode: https://opncd.ai/share/81jJAiio
• https://github.com/anomalyco/opencode/blob/dev/packages/opencode/src/tool/read.ts#L206-L206
• https://nodejs.org/api/path.html#pathisabsolutepath

[nickjvandyke]

(maybe there's a neovim API for this, I'm not sure).

There is, and it's not the default to use ~/ - I added that option for shorter, more readable messages. But didn't expect it to cause this! 😅

I pushed a fix just now. Great digging!

I'll explore making the path relative to the server's CWD later. The logic is simple, but requires some structural changes; atm Context is not aware of the server it's formatting for.

[lungsin]

Nice! Thanks a lot for your help! ❤️

[nickjvandyke]

Created #272 for visibility 🙂

[lungsin]

Even the message endpoints don't support explicit file refs.

Sorry for necroing a little bit. I opened an issue on the opencode repo for requesting a tui API for attaching file: anomalyco/opencode#32963.

There's actually a way to send a message with attachments using /session/:id/message, but it's not a TUI API and it directly submits the prompt to the opencode backend (not sure what to call it). So it's not fit for our usecase, since we want to manipulate the TUI itself (append without submitting, etc).

[lungsin]

Anyway, I'll open a new issue / discussion about it once the opencode's API is ready.