stacklok / stacklok/mecatl

mecatui: hide session ID by default and expose it through /session during runs

Open
#1,606 0 comments 0 reactions 1 assignee View on GitHub

@jbeda is already working on this.

Since Sep 15, 2026.

Dominant language
Go
Stars
152
Forks
16
Avg merge
14h 48m
Merged PRs (30d)
536

Description

Problem

mecatui currently exposes the session ID/short handle by default in both its in-app header and terminal-title composition. This consumes scarce title/header space and makes the identifier visually prominent even when the user does not need it.

When the agent is busy, however, the user needs a reliable way to retrieve the full session ID for support, reconnect/recovery, or cross-client operations. The /session command should remain usable while a run is active so the ID can be captured without waiting for the agent to finish.

Requested behavior

  1. Remove the session ID/short handle from the default in-app header.
  2. Remove the session ID/short handle from the default terminal-title composition.
  3. Ensure /session can run while the agent is busy and renders the current session’s ID.

Acceptance criteria

  • During an active agent run, entering /session returns/displays the current session ID without cancelling, queueing behind, or otherwise disrupting the active run.
  • The default in-app header does not display the session ID or short handle.
  • The default terminal title does not include the session ID or short handle.
  • Session identity remains available through /session for users who need it.
  • Add regression coverage for the busy-state /session behavior and the default header/title presentation.

Scope

This is intentionally about default presentation and session-ID discoverability. It does not change session identity, recovery semantics, or the terminal-title OSC behavior.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.