New Chat Greetings

Verification report for issue #676. Claude.ai was inspected on July 3, 2026, and Tegy's new chat empty state was updated to use a deterministic, time-aware greeting. Follow-up issue #679 refined the copy so Tegy keeps the interaction pattern without copying Claude's exact tone.

Claude.ai Evidence

Claude reads the name from the account bootstrap payload display_name; the observed account value was already tornikeo, so no page-load LLM inference was needed. This proves where the page read the value from, not how Claude originally created that account-level display name.
The greeting list is bundled client-side in the observed Claude build. It filters templates by local time of day, weekday, whether a display name exists, whether the account is older than one day, and incognito state.
The final choice is deterministic for the day using a simple string hash over date, time bucket, and name mode. Repeated reloads rendered the same greeting.

Tegy Adaptation

Tegy now derives the greeting name from session.user.name, then falls back to the email local-part.
The frontend uses a Tegy-specific professional template set aligned with the landing page: decisions, assumptions, pressure-testing, rigor, and defensibility.
The empty composer shows a dynamic workspace pill from session.org.name. It does not show a static logo; the session does not currently expose an org logo URL.
Decorative greeting icons were removed so the empty state reads as a focused work surface rather than a playful chat splash.

All Tegy Greeting Templates

{name} means the value derived from session.user.name, with email local-part as the fallback. The final greeting is selected deterministically from the eligible rows for the current local time bucket and name mode. This is the complete Tegy template set; Tegy does not reproduce Claude's exact phrase table.

Eligibility	Name Mode	Template
Morning	With name	{name}, what decision needs structure?
Morning	With name	Start with the assumptions, {name}
Morning	With name	Set the decision bar, {name}
Monday morning	With name	{name}, make the week's first decision defensible
Friday morning	With name	{name}, close the week with a clear call
Weekend morning	With name	{name}, sharpen the next move
Afternoon	With name	What needs pressure-testing, {name}?
Afternoon	With name	{name}, bring the messy problem
Afternoon	With name	Turn the problem into a decision, {name}
Returning afternoon	With name	{name}, continue from the open assumptions
Evening	With name	{name}, make the next call clear
Evening	With name	Pressure-test the plan, {name}
Evening	With name	What decision needs rigor, {name}?
Returning evening	With name	{name}, pick up the strategy thread
Late night	With name	{name}, capture the unresolved call
Late night	With name	List the assumptions, {name}
Morning	No name	What decision needs structure?
Morning	No name	Start with the assumptions
Morning	No name	Set the decision bar
Monday morning	No name	Make the week's first decision defensible
Friday morning	No name	Close the week with a clear call
Weekend morning	No name	Sharpen the next move
Afternoon	No name	What needs pressure-testing?
Afternoon	No name	Bring the messy problem
Afternoon	No name	Turn the problem into a decision
Returning afternoon	No name	Continue from the open assumptions
Evening	No name	Make the next call clear
Evening	No name	Pressure-test the plan
Evening	No name	What decision needs rigor?
Returning evening	No name	Pick up the strategy thread
Late night	No name	Capture the unresolved call
Late night	No name	List the assumptions
Fallback	With name	What decision should Tegy pressure-test, {name}?
Fallback	No name	What decision should Tegy pressure-test?

Local Verification

Playwright mocked the local API with a RocketMinds session and checked desktop plus mobile layout bounds. Browser console errors after the clean rerun: zero. Follow-up verification also checked that the greeting heading and workspace pill contain no static svg or img icons.

Desktop

1280 x 760 viewport.

Mobile

390 x 844 viewport.