Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE] File Refresh

Open
#137 4 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua
Domain
tooling

Research direction

Start by reading lua/claude-code/file_refresh.lua in the referenced claude-code.nvim implementation and inspect this plugin's Claude Code edit flow. Done means buffers changed by Claude Code update automatically when revisited, without enabling a global Neovim refresh setting; verify the behavior against the existing :ea alternative.

Written by the indexing model from the issue text.

Description

Feature Description

Is there a file refresh system like in the other claude code neovim plugin? I searched through the issues but I couldn't find any complaints about it. It's not a big deal to type :ea after going back to an editing buffer after claude makes some edits, but it would be nice if this happened automatically (and I would prefer if it was dependent on claude code making a change and not a global neovim file refresh setting that was always running).

Use Case

This is just a small convenience which keeps the buffers that claude code is changing live updating.

Proposed Solution

If this is already possible somewhere, please let me know. Otherwise I can try to port the solution from the other project and make a PR.

Alternatives Considered

typing :ea reloads all buffers from the files on disk

Additional Context

N/A

Dominant language
Lua
Stars
3.1k
Forks
219
PR merge metrics
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/claudecode.nvim

All issues in coder/claudecode.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.