Improve Telegram ready notifications with project/session context

[Shujakuinkuraudo]

Motivation

Telegram ready notifications currently use a very generic message:

It's ready!

<agent> is waiting for your command

When multiple HAPI sessions are running across different machines or projects, these notifications look almost identical. It is hard to tell which repository, working directory, machine, or task the notification belongs to without opening each session.

Proposal

Add more project/session context to Telegram ready notifications and related action-required notifications. Useful fields could include:

• Session title or tag, if available
• Project/repository name
• Working directory basename or relative path
• Machine/host name
• Model/agent name, if relevant
• A short preview of the last user message or task prompt

For example:

Ready: infra on pc

Codex is waiting for your command
Session: rotate HAPI secrets
Path: ~/infra

Or, for permission requests:

Action required: infra on pc

Codex requests permission
Session: rotate HAPI secrets
Path: ~/infra

Notes

This would make Telegram notifications much more useful for users who keep several sessions active at once. It would also reduce unnecessary Mini App opens just to identify which session generated the notification.

A minimal first version could simply include session title/tag plus machine name, falling back to the current text when context is unavailable.

[github-actions]

Confirmed. The current Telegram ready notification is generic: sendReady() hard-codes It's ready! plus the agent label, and does not include session path, session name, machine, or prompt preview.

Permission notifications already include a session display name and the first pending tool request, but I did not find machine/path context in that formatter. The requested context appears available from existing data: session metadata includes path, host, name, summary, machineId, and flavor; machine metadata includes displayName, host, and workspaceRoot.

A minimal implementation looks scoped to the Telegram notification formatting layer: reuse the existing session name helper for ready notifications, add path/machine fields where present, and keep current text as fallback when metadata is missing.

Relevant code:

• hub/src/telegram/bot.ts:190 - sendReady(session) builds Telegram ready notifications.
• hub/src/telegram/bot.ts:209 - current ready text is hard-coded as It's ready! plus agent name.
• hub/src/telegram/sessionView.ts:18 - permission notification formatter.
• hub/src/telegram/sessionView.ts:20 - permission notification includes Session: ${name} today.
• hub/src/notifications/sessionInfo.ts:4 - existing session display name fallback: metadata name, summary, path basename, then session id prefix.
• shared/src/schemas.ts:22 - session metadata fields available for notification context.
• hub/src/sync/machineCache.ts:6 - machine metadata fields available for machine display context.
• hub/src/notifications/notificationHub.ts:67 - ready events trigger ready notifications.
• hub/src/notifications/notificationHub.ts:102 - new permission requests trigger permission notifications.

---

HAPI Bot