Skip to content

feat(examples): support conversation_title in title.sh and update docs - #990

Open
toyo30 wants to merge 1 commit into
google-antigravity:mainfrom
toyo30:feat/title-conversation-name
Open

toyo30 wants to merge 1 commit into
google-antigravity:mainfrom
toyo30:feat/title-conversation-name

Conversation

@toyo30

@toyo30 toyo30 commented Sep 10, 2026

Copy link
Copy Markdown

Description

Extends the window title example script (examples/title/title.sh) and documentation to extract and display the active conversation_title (or conversation_name) in the terminal window title when set (e.g. via /rename or /title).

Motivation

When working with named sessions, having the current conversation name reflected in the terminal window title (e.g. 🏃 working | homepage (auth-refactor)) makes multi-session navigation much clearer and integrates directly with the CLI conversation lifecycle.

Changes Made

Testing

  • Tested title.sh with payload containing conversation_title:
    echo '{"agent_state": "working", "workspace": {"current_dir": "/Users/user/project"}, "conversation_title": "my-task"}' | bash examples/title/title.sh
    # Output: 🏃 working | project (my-task)
  • Tested title.sh with payload without conversation_title:
    echo '{"agent_state": "idle", "workspace": {"current_dir": "/Users/user/project"}}' | bash examples/title/title.sh
    # Output: 😴 idle | project

- Extract conversation_title (or conversation_name) from stdin JSON payload
- Append formatted conversation title to window title when present
- Update README documentation with new title format
- Relates to google-antigravity#989
@google-cla

google-cla Bot commented Sep 10, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant