nickjvandyke/opencode.nvim

bug: `<file>.new` buffer persists after edit request diff

Closed

#258 opened on May 9, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Lua (127 forks)auto 404
buggood first issue

Repository metrics

Stars
 (3,504 stars)
PR merge metrics
 (Avg merge 2d 22h) (9 merged PRs in 30d)

Description

Describe the bug

When we display a diffpatch in response to an edit request, Neovim creates a <file>.new buffer. Even after the diff is closed, the .new buffer appears in e.g. buffer and file pickers, which is confusing and noisy.

Steps To Reproduce

  1. vim.g.opencode_opts.events.permissions.edits.enabled = true
  2. ask opencode to edit a file
  3. Respond to the edit request via the diff tab (haven't checked whether this only happens with certain responses)

Expected Behavior

<file>.new should be deleted from the buffer list.

See plugin/events/permissions/edits.lua

Contributor guide

Research direction
Inspect `plugin/events/permissions/edits.lua` to find where `<file>.new` buffer is created and ensure it is closed or wiped after the diff is dismissed. Look for buffer cleanup logic and add a wipe command after diff closes.
Tech stack
lua
Domain
developer experiencetooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
NeovimLua
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60