anomalyco / anomalyco/opencode

[FEATURE]: Surface recent directories in the existing /move picker

Open
#50,142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
Avg merge
7h 2m
Merged PRs (30d)
384

Description

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 existing /move picker already knows project directories and session subdirectories. I would like it to surface a small Recent group derived from existing session metadata, so switching back to recently used directories inside the current project does not require hunting through the full list.

Proposed scope:

  • reuse existing session/project directory data; no new persistence
  • same-project only
  • exclude the current directory and deduplicate paths
  • keep the existing moveSession flow unchanged
  • keep the TUI SDK-only / remote-safe
  • no new slash command

Rough UX:

Move session

Current
  ~/code/project

Recent
  ~/code/project/backend
  ~/code/project/agent-runtime

Other
  ~/code/project/worktree-a

I recently implemented the same recent-directory picker idea in Oh My Pi (can1357/oh-my-pi#12497), where it made repeated project navigation much faster on Windows/PowerShell.

I am not proposing to copy that implementation here. OpenCode already has a more complete move-session architecture, so this would only change how destinations are surfaced.

Related but different:

  • #8541 proposed directory navigation inside the session dialog
  • #43223 proposes a new /cd command/tool
  • this request only enhances the existing /move picker

If the core team likes the UX, I can prepare a small implementation after design approval.

Contributor guide

Open the 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.

Research direction

Start by locating the existing /move picker, its session/project directory metadata, and the moveSession flow. Confirm how destinations are currently surfaced and keep the change within the existing TUI SDK-only, remote-safe path. Done means a same-project Recent group excludes the current directory, deduplicates paths, reuses existing metadata, and leaves the move flow unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.