Configurable Status Lines in Cursor Agent

Ideas Feature Requests
,
1

Feature request for product/service

Cursor CLI

Describe the request

Feature request: User-configurable composer bar status line

Where to post: Cursor Forum → Ideas → Feature Requests
Suggested tags: composer, layout, ui

Title

User-configurable status line in composer bar (hostname, session id, repo, branch, tag)

Summary

Make the text shown in the composer bar (the line below the prompt that currently shows things like “Auto · 8.3% · 1 file edited” and “/ commands · @ files · ! shell · ctrl+r to review edits”) user-configurable, so we can optionally display context such as:

  • Hostname (machine name)
  • Session ID (e.g. UUID for the current Cursor session)
  • Repo (current workspace / repo name)
  • Branch (current git branch)
  • Tag (git tag on HEAD, if any)

Desired format example

hostname | session_id | repo | branch | tag

Example: GS00507 | 5bf723fc-e8ff-4f96-94ec-e20686d40bc7 | ai-usage | main | 0.15

Precedent

Claude Code (Anthropic’s AI coding environment) already shows a status line in this style (hostname | repo | branch | tag). Users who switch between Claude Code and Cursor would benefit from the same kind of context in Cursor.

Why

  • Multi-machine / multi-session: Quickly see which host and session you’re in when switching machines or windows.
  • Repo/branch/tag at a glance: Avoid running git in the terminal just to confirm repo, branch, or tag when pasting snippets, writing docs, or filing bugs.
  • Consistency: Same status format across team or org for support and debugging.

Proposed implementation

  • A setting (e.g. cursor.composer.statusLineFormat or similar) that accepts a template string with placeholders, for example:

    • {hostname} — OS hostname
    • {sessionId} — current Cursor session ID
    • {repo} — workspace folder/repo name
    • {branch} — current git branch
    • {tag} — tag on HEAD (e.g. from git describe --tags --exact-match HEAD), or empty if none

  • Default could be the current behavior (no change); users who want this context opt in by setting the template.

  • Optionally: a simple preset like “Full context” that uses the format above.

Alternatives considered

  • Fixed format: Less flexible; a configurable template supports different teams’ conventions.
  • Only in status bar: Composer is where we’re typing and making decisions; having repo/branch/tag there is more useful than only in the window status bar.

Thanks for considering this.

2 Likes
3

Yes! Please consider this! Claude Code has it and it is very useful