Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature]: New widgets in the same tab should inherit the working directory of the active terminal

Aperta
#3,483 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go

Direzione di ricerca

The issue names no files, tests, or code entry points, and provides no implementation suggestion. Start by locating the code that creates Terminal and Files widgets and tracks active tabs or terminals; done means new widgets in a tab use the most recently active terminal's working directory, with behavior verified for both widget types.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement triage
Feature description
Feature Request: Make new widgets in the same tab inherit the active terminal's working directory

Environment

  • Platform: Wave Terminal
  • OS: macOS 26.6.2 (arm64)
  • User: liuishihua
  • Current tab state:
    • (1d08f870) local CLI terminal (fish 4.6.0)
    • Running command: claude
    • Working directory: /Users/gzxworkspace/2026/gzxHrApp2026

Problem

In the same tab, when I already have a terminal opened in a certain working directory, if I then open:

  • a new Files widget, or
  • a new Terminal widget,

these new widgets do not automatically use the same working directory as the existing terminal. This leads to extra navigation steps every time I open a new widget in the same tab.

Expected behavior

Within a single tab:

  • When I open a new Terminal widget, it should inherit the working directory of the most recently active Terminal widget in that tab (e.g. /Users/gzxworkspace/2026/gzxHrApp2026).
  • When I open a Files widget, it should also default to the same directory as the active terminal in that tab.

In other words, each tab should effectively have a "current working directory context", and new widgets created in that tab should follow it.

Why this is useful

  • Reduces repetitive cd operations and manual navigation in Files.
  • Makes tabs feel like project/workspace scopes: when I'm in a project tab, anything I open there (Files, new terminals) automatically stays in that project's directory.
  • Improves consistency and predictability of how widgets behave in the same tab.

Nice-to-have options

  • A setting to toggle this behavior:
    • "New widgets inherit active terminal working directory (per tab)"
  • Optionally, a way to set a tab-level "project root" that all new widgets default to.

Thank you for considering this feature!

功能需求:同一个 Tab 中新建的 widget 继承当前终端的工作目录

环境

  • 平台:Wave Terminal
  • 系统:macOS 26.6.2 (arm64)
  • 用户:liuishihua
  • 当前 Tab 状态:
    • (1d08f870) 本地 CLI 终端(fish 4.6.0)
    • 正在运行命令:claude
    • 工作目录:/Users/gzxworkspace/2026/gzxHrApp2026

问题描述

在同一个 Tab 中,当我已经有一个终端在某个工作目录下时,如果我随后打开:

  • 新的 Terminal widget,或者
  • 新的 Files widget,

这些新 widget 并不会自动使用当前终端的工作目录,需要我再次手动 cd 或在 Files 里重新导航,比较繁琐。

期望行为

在单个 Tab 内:

  • 新建 Terminal widget 时,默认继承该 Tab 内最近一个活动终端的工作目录(如 /Users/gzxworkspace/2026/gzxHrApp2026)。
  • 打开 Files widget 时,也默认进入当前活动终端所在目录。

也就是说,希望每个 Tab 有一个“当前工作目录上下文”,在这个 Tab 里新建的任何 widget(Terminal / Files)都自动跟随这一目录。

这样做的好处

  • 减少重复 cd 和在 Files 中手动切换路径的操作。
  • 让 Tab 更像是“项目 / 工作区”的概念:进入某个项目的 Tab 后,在里面开任何 widget 都自动落在该项目目录下。
  • 行为更一致、更符合直觉。

可选增强

  • 提供一个设置开关:
    • 「同一 Tab 中新建 widget 继承当前终端工作目录」
  • 也可以考虑支持为 Tab 设置一个“项目根目录”,所有新 widget 默认使用该根目录。

感谢考虑这个需求!

Implementation Suggestion

No response

Anything else?

No response

Lingua principale
Go
Stelle
22.3k
Fork
1.1k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wavetermdev/waveterm

Tutte le issue di wavetermdev/waveterm

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.