Show endpoint and tips when emulator is already running

[gtsiolis]

This will:

1. Show the endpoint, web app URL, and a random tip when the emulator is already running, matching the start output.
2. Render the "already running" message as a note (> Note:) instead of a plain info line

BEFORE	AFTER

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 1a21200a-816f-415b-903b-437f0b003afc

📥 Commits

Reviewing files that changed from the base of the PR and between d2de6da and 386ce82.

📒 Files selected for processing (2)

• internal/container/start.go
• internal/ui/app.go

---

📝 Walkthrough

Walkthrough

The changes modify the post-start output flow to pass endpoint and web app URL information through the container start process. When containers are already running, message output switches to note-level severity with endpoint details emitted. The UI layer adds a new message handler to hide headers when note-severity messages are received.

Changes

Cohort / File(s)	Summary
Container start flow internal/container/start.go	Start function now passes LocalStackHost and WebAppURL to selectContainersToStart. When a running container is detected, the message type changes from info to note, and endpoint host resolution with emitPostStartPointers is invoked before continuing.
UI message handling internal/ui/app.go	Added hideHeaderMsg message type handled in App.Update to set a.hideHeader = true. For output.MessageEvent, a command is conditionally scheduled when severity is output.SeverityNote to trigger header hiding.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• List endpoint and web app on start #114: Modifies post-start output flow to emit webAppURL/endpoint information and adjusts message-severity handling in a similar manner.

Suggested reviewers

• carole-lavillonniere
• silv-io
• anisaoshafi

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: showing endpoint and tips when the emulator is already running, which matches the primary modifications in the PR.
Description check	✅ Passed	The description is clearly related to the changeset, explaining the three main objectives and providing visual before/after comparisons of the changes made.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch des-194-improve-output-when-emulator-is-already-running

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[anisaoshafi]

UX wise looks good 🧹

Question: This is going to hide the TUI header for all SeverityNote messages, not only in the case emulator is running. Is this expected @gtsiolis?

[gtsiolis]

Good point, @anisaoshafi. Now that the banner is more functional with plan and config path with #180, we can leave it as is for now. In the future we may add a boolean to hie the banner per case.

Cc @carole-lavillonniere

[carole-lavillonniere]

We should check the result dnsOK of ResolveHost like we do line 227 in current file

[gtsiolis]

Nice one, added in 41add77.

[gtsiolis]

Thanks both, @anisaoshafi and @carole-lavillonniere!

[anisaoshafi]

LGTM! ✨