Issue Station
Sign In
Tools hereToolbox

gemini-cli - ✅(Solved) Fix Feature Request: Display system hostname in the bottom status border [1 pull requests, 2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25661•Fetched 2026-04-20 12:15:48
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
ejgardner413ejgardner413
Participants
AdityaSharma-Git3207AdityaSharma-Git3207ejgardner413ejgardner413gemini-cli[bot]gemini-cli[bot]
Timeline (top)
commented ×2cross-referenced ×1issue_type_added ×1labeled ×1

Fix Action

Fixed

PR fix notes

PR #25663: feat(cli): add hostname to footer status bar

Description (problem / solution / changelog)

Summary

Adds the current system hostname to the persistent bottom status border.

This helps users quickly distinguish between multiple Gemini CLI sessions running across SSH hosts, virtual machines, containers, or remote systems.

Details

This change adds a new footer item: hostname.

  • Added hostname to available footer items
  • Added hostname to the default footer order
  • Added hostname to legacy-derived defaults for backward compatibility
  • Displays hostname using Node's built-in os.hostname()

The hostname uses the existing footer column layout, so current overflow and spacing behavior remain unchanged.

Related Issues

Closes #25661

How to Validate

  1. Run Gemini CLI locally.
  2. Check the persistent bottom status border.
  3. Confirm a new host field is shown.
  4. Verify the displayed hostname matches the current machine.
  5. Resize terminal width and confirm footer layout still behaves correctly.

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

Changed files

  • packages/cli/src/config/footerItems.ts (modified, +7/-0)
  • packages/cli/src/ui/components/Footer.tsx (modified, +14/-0)
RAW_BUFFERClick to expand / collapse

What would you like to be added?

Please add the current system's hostname to the persistent bottom status border of the Gemini CLI interface. Ideally, this would be displayed as a new column alongside the existing status indicators (workspace, sandbox, and model).

Why is this needed?

For users who run Gemini CLI simultaneously across multiple remote hosts, SSH sessions, or virtual machines, it becomes very difficult to keep track of which instance is currently active in the terminal. Without a visible hostname indicator, there is a high risk of context confusion, which can lead to accidentally executing commands, modifying scripts, or querying files on the wrong machine. Displaying the hostname directly in the CLI's UI would provide immediate situational awareness and vastly improve the multi-host workflow.

Additional context

No response

extent analysis

TL;DR

Add the system's hostname as a new column in the Gemini CLI interface's bottom status border to improve multi-host workflow situational awareness.

Guidance

  • Identify the code responsible for rendering the bottom status border in the Gemini CLI interface to determine the best approach for adding a new column.
  • Investigate available system APIs or libraries that provide the hostname, such as os.hostname() or equivalent, to fetch the current system's hostname.
  • Consider the UI design implications of adding a new column, ensuring it aligns with existing layout and styling conventions.
  • Evaluate potential security or privacy concerns related to displaying the hostname in the CLI interface.

Example

No code example is provided due to lack of specific technical details about the Gemini CLI interface implementation.

Notes

The feasibility of this addition may depend on the Gemini CLI's architecture, available APIs, and design constraints. Further investigation into the codebase and potential dependencies is necessary.

Recommendation

Apply workaround: Modify the Gemini CLI interface to display the hostname as a new column, if technically feasible, to improve user experience in multi-host environments.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#agent execution#callback error#memory management#API rate limit#retriever error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING