Repository navigation
Feature request: show session working directory in the footer #512
Description
Feature request
Show the session's working directory in the footer (the bar between output and input that currently shows model/mode), e.g. on the left side, which is mostly empty today.
When running multiple session tabs bound to different directories (or multiple projects in one Neovim instance), there is no way to tell at a glance which directory the visible session belongs to. The session's directory is its most important property — it decides where the agent reads and writes files.
Suggested shape: a config flag like ui.display_directory = true, rendering something like repo:branch (or a ~-shortened path outside git repos) on the footer's left side.
For reference, I do this in my config by wrapping footer.set_content: prepend a repo:branch label (resolved from git rev-parse --git-common-dir --abbrev-ref HEAD, cached per directory) and shrink the middle padding by the label width so the right side never clips. Happy to share the snippet or turn it into a PR if you're interested.
Activity
sudo-tee commentedon Oct 6, 2026
I would prefer providing hooks for people to modify the
topbarandfooteryou would get a list of segmets and return a list of segments ?since a cwd can take space and not everybody uses worktree, it's better to add custom hooks instead.
Whould this work for you ?
wzj-zz commentedon Oct 6, 2026
Yes, hooks for
topbar/footersegments would work great for me — actually a better design than a built-in cwd option, since it covers arbitrary segments (git status, etc.) without you having to anticipate every use case.My concrete use case for reference: I prepend a
repo:branchlabel on the footer's left side (resolved from the session's cwd, cached per directory), and shrink the middle padding by the label width so the model/mode segments on the right never get clipped. With asegments in -> segments outhook this becomes a plain config function instead of a wrapper, which is exactly what I want.Happy to test it and give feedback once the API shape lands.
sudo-tee commentedon Oct 6, 2026
You can try #514
if you want to let me know if it works for you :)
sudo-tee commentedon Oct 6, 2026
The MR has been merged :)