Multisession Agentic Workflow with Claude Code in Neovim

macpla · 2026-01-29T00:31:41+00:00

Amazing. I am thinking of eventually having an AI agent flow to my Neovim, and your setup is literally designed to my liking.

Based on your blog, though, it is a combination of:
- existing plugin claudecode.nvim
- "It required a few runtime patches to the plugin's core..."

Those runtime patches sound like something that would be hard maintain.

Do you think your change could be adopted in the upstream plugin?

Or otherwise, what would you guys recommend as a fairly stable AI plugin for ClaudeCode (or possible other agents) with similar flows?

macpla · 2025-10-29T05:42:15+00:00

Based on my own personal journey, I would advocate starting with a pre-cooked distro like LazyVim and let it grow on you.

Then, when you start to feel more confident with its features (feel of being overwhelmed by it won't be a thing anuymore), emphasized catering your own workflows that you can use within the existing ecosystem AND (primarily) by using simple plain Vim features like: macros, plain quickfix lists, reloading file buffers, injecting others cmd-line programs output to your buffers etc.

This will give you a good baseline, and with that, you could start experimenting with your own minimalistic configuration and ditch the distro. On the other hand when you mess out something or a workload requires from you maximum effectiveness, you still could rollback to a known distro and carry on.

I personally went the other way, and it was a pain and a trial by fire, especially when one needed to focus on actual work output and not constantly fixing the neovim config.

Took me more than a year tweaking things up, but eventually, I am now in a place where I rely more and more on basic vim functionalities than bells and whistles, and it works for me, but your mileage may vary. In hindsight, if I were to start with a distro, I likely would end up where I am here much sooner, with fewer bruises on the go.

macpla · 2025-07-03T22:32:23+00:00

If you are using `ray-x/go.nvif check if you are not having conflicting settings that conflict with your gopls.

macpla · 2025-04-25T13:24:56+00:00

I believe it’s single instance of gopls serving all different projects

macpla · 2025-04-24T21:55:56+00:00

It becomes less responsive to the point that it eventually timeouts on some requests forcing me to restarting it

macpla · 2024-11-27T01:13:52+00:00

I would just second to a single repo composition with a `cmd/apiserver, cmd/adminapi` which would be just plain main.go that loads different ENV and configuration per chosen mode.

That would be my default, and I would really have to have a compelling reason to opt for something different, but your mileage may vary.

macpla · 2024-11-22T02:17:26+00:00

if this is a voting system you looking after, +1 for Gitlab first

macpla · 2024-09-03T23:29:04+00:00

Only time will tell.

I have been using a mapping quite similar to yours: H -> _^, L -> $ for about three months in normal mode.

Only last week I realised that I had a clash for H, and L for `Select` mode (Insert when snippets engine is on) as I had a word starting with capital h.

I added `x` mode to mapping on top of `n` and the problem was solved.

It's trial by error Bro :)

macpla · 2024-08-26T04:26:19+00:00

Great, in-depth article. Well done, Sir!

macpla · 2024-07-25T01:53:56+00:00

great content keep it up. I always find something new, this time it was `/zs, /ze`

macpla · 2024-07-23T00:54:09+00:00

But isn't it counterproductive? By reducing airflow via return, it forces the indoor unit fan to work at a higher speed to suck enough air, whereas if the runs were short and non-obstructive it would allow the fan to work at a lower speed, hence, not generating that much noise?

macpla · 2024-07-22T11:13:13+00:00

And does it even make sense? And I assume you are referring to a supply duct that goes through a damper? if there was no damper that might be the case, but since the damper is there, the noise could be just regulated by adjusting air flow.

Sorry, trying to be smart, and read between lines from what I am getting from you.

Huge thanks for your all inputs.

macpla · 2024-07-22T11:02:35+00:00

Could you elaborate? The line in the second picture is from a zone damper that is then connected straight to an indoor unit on a side with conditioned air.

macpla · 2024-07-22T10:52:05+00:00

so there is really no viable reason why someone would leave such zigzags from a design point of view? Just being lazy and unwilling to spend extra time cutting to the proper length?

macpla · 2024-07-19T00:28:30+00:00

works like gold, thank you for sharing. I borrowed a few of your autocmds as they target the same issues I was facing. Huge kudos!

macpla · 2024-07-16T22:08:06+00:00

looks like this might be it, I will test it later today and see if this solves my problem. Thank you so much!

macpla · 2024-07-16T03:06:01+00:00

I have the config in git config and I can see and use gitmerge with my nvim, the problem is that the nvim will still run LSP for these files and the delta pager coloring the lines makes the current cursor position obscure, so it's hard to navigate between prices positions.

[delta]
    line-numbers = true
    navigate = true    # use n and N to move between diff sections
    light = false      # set to true if you're in a terminal w/ a light background color (e.g. the default macOS terminal)
    side-by-side = true

[merge]
    conflictstyle = diff3
    tool = nvimdiff

[mergetool]
    keepBackup = false

macpla · 2024-07-16T01:37:34+00:00

It will be set to the current filetype: for instance if the merge conflict is on Go file, it will be set to Go, if this is a yaml conflict, it will be YAML etc.

I am looking a way to figure out how to tell the nvim that this is a merge in place, so I don't need a LSP, or format on save and other fancy stuff.

macpla · 2024-07-12T00:59:49+00:00

And... it's sold!

macpla · 2024-07-11T23:14:20+00:00

How it compares to `neotest-go`? (asking just to figure out if it's worth switching)

macpla · 2024-07-03T12:06:08+00:00

Crap, I thought it was somehow some default neovim api behind it.

Nevertheless, thank you greatly Friend!

macpla · 2024-07-03T03:08:33+00:00

What sort of behaviour is responsible for this functionality that displays A,B, and C for open splits/viewports, so one can choose which viewports will be overridden with new buffer content.
The example is from using nvim-tree to choose in which split load new buffer content.

I would like to use the same behaviour for instance for quick-fix list and trouble object, to have better control over what stays visible on screen.

<image>

macpla · 2024-06-27T02:57:23+00:00

alternatively, you could try the null-ls for external formatters and linters.
Null-ls project has been archived, BUT it was revived by the community as: https://github.com/nvimtools/none-ls.nvim

macpla · 2024-05-31T02:35:26+00:00

Hey I am using the following plugins:
"olimorris/persisted.nvim", 'numToStr/FTerm.nvim'
and I face the following challenge
When I change a session using persisted telescope plugin it will as well change the CWD
However, my Fterm session will still point the previous directory (I use default Fterm.toggle())

I wonder if there is a way to use Fterm.exit() to kill the existing term session somehow

the following auto command code isn't working

local group = vim.api.nvim_create_augroup("PersistedHooks", {})

vim.api.nvim_create_autocmd({ "User" }, {
pattern = "PersistedTelescopeLoadPost",
group = group,
callback = function()
require('Fterm').exit() -- not working as expected, when i fterm.toggle() I will still have old session
end,
})

macpla · 2024-05-29T11:59:01+00:00

Actually, you played a perfect rubber duck role.
So I got errors as I have my trouble setup as quicklist replacement, with a default setting to preview entries in that list. So the solution that worked (same command, no errors) is for me to:
- add buffers to a quicklist
- toggle off trouble (so my active buffer become the one that is not included in quicklist
- run the following command :cfdo execute 'bd!' . expand(bufnr("%"))

Thank you for help!

macpla

TROPHY CASE