[FEATURE]: · Issue #57780 · anomalyco/opencode · GitHub
Skip to content

[FEATURE]: #57780

Open
Open

Description

@KamranM5

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

The file tree is read-only. To rename or delete a file I have to switch to Explorer or a terminal, or ask the agent and spend tokens on it.

I'd like to start with just these two actions:

  • Hovering a row shows a pencil (rename) and a trash can (delete).
  • Rename turns the name into an input. Enter confirms, Escape cancels, and the open tab picks up the new name.
  • Delete asks for confirmation first.

I'm not asking for an editor, drag and drop or multi-select here. If this goes in, those can be separate issues.

Earlier requests: #26918 (context menu with rename and delete) and #26970 (file editor) were closed by the stale bot with no maintainer decision, and #29930 (inline file editing) was closed as not planned. PR #39811 added rename and delete but was auto-closed after 2 hours because its description didn't follow the template. Only the bot commented on it.

I have this working in a separate project, and the screenshots and recording below come from it. I'm willing to build it in opencode: a small PR against dev, template filled in, screenshots for the UI change. Please assign me if you're open to it.

Two questions:

  1. Is the file tree meant to stay read-only?
  2. Should delete use the OS trash where possible, or remove files permanently after confirmation?
Image Image
demo.mp4

Activity

  1. opencode-agent commented on Oct 21, 2026

    @opencode-agent
    Contributor

    Thanks for the detailed proposal, the screenshots, and the offer to build it!

    To restate it: you'd like the app's file tree to show rename and delete actions on hover. Rename would edit the name inline, with open tabs following the new name, and delete would ask for confirmation first. Editing, drag and drop and multi-select are left out on purpose.

    The maintainers will consider it, including your two questions: whether the tree should stay read-only, and whether delete should use the OS trash. It's best to wait for their answer before starting the PR.

    Related issues and PRs:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions