docs: add Angular chat app tutorials for AG-UI and LangGraph - #814
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Two net-new tutorials that build a chat app rather than a chat surface, differentiated by what each protocol actually offers: - LangGraph: multi-thread app with a conversation sidebar backed by the server thread API, server-written titles, and URL-as-source-of-truth thread routing. - AG-UI: browser-owned client tools (action/view/ask) rendering real Angular components inline, plus agent-shared state. Both were scaffolded, built, and driven end-to-end against live backends before writing; the code in each post is the code that ran. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
added a commit
that referenced
this pull request
Aug 14, 2026
Pushes to main do not cancel in-progress runs (cancel-in-progress is true only for pull_request), so runs serialize and a slower older run can reach its deploy job long after a newer commit has already shipped. It then rebuilds --prod from its own older checkout and promotes it, silently overwriting production. Observed 2026-08-14: the CI run for #813 promoted at 04:37, replacing the deployment that had published two blog posts from #814 at 04:13. Both posts 404'd until the next merge happened to redeploy them. Nothing failed; CI was green the whole time. Add a freshness check to each job that promotes: resolve the current tip of main and skip promotion when it no longer matches github.sha, logging a warning so the skip is visible. Setup and change-detection steps still run; only the production-touching steps are gated. Covers all five promotions — website, cockpit, Angular examples, the canonical demo, and the ag-ui demo. The last of those was found by the new spec assertion, not by reading the file. Notes on the implementation: - Uses `git ls-remote`, not `git fetch --depth=1`: a shallow fetch would mark the deploy job's full clone shallow and break the --affected history checks that run right after it. - Fails loudly when the tip cannot be resolved, rather than treating an empty result as "stale" and silently skipping every deploy. - Gates the demo build-stamp verification too, since it asserts the deployed SHA equals this run's SHA. This narrows the race to the build window rather than closing it entirely; a commit landing mid-build can still be overtaken. Fixing that completely means either serializing promotions or having Vercel resolve the alias, which is a larger change. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two net-new tutorials that build a chat app rather than a chat surface, differentiated by what each protocol actually offers.
action/view/ask) rendering real Angular components inline, plus agent-shared stateThey sit alongside the May posts rather than replacing them, and cross-link instead of re-explaining the protocol event model. Each names the other's strength: server-backed thread history is a LangGraph capability (AG-UI defines no thread-lookup endpoint), and protocol portability is AG-UI's.
Both are
draft: false, featured: false— live on merge, without taking the featured slot from the Strands post.Verified, not just written
Every snippet came from code that ran. Both backends (
langgraph devwith a real graph; FastAPI +ag-ui-langgraph) and both Angular apps were scaffolded fromng newagainst the published@threadplane/*@0.0.57packages and driven in a browser with a liveOPENAI_API_KEY.Confirmed end-to-end: thread restore, URL stamping, reload survival, server-generated titles,
add_linkmutating a browser signal store, aviewcard mounting inline, and anaskcard resolving and freezing the transcript.Three findings surfaced only by running it, and all three fed #813 (already merged):
<chat-sidenav>has no default slot, client-tool results carry no tool name, andng new's default 1 MB budget fails the build first.One recommendation was cut after testing disproved it: a "just refresh twice" fix for the thread-title lag. A 1.5s delay, a 4s delay, and a 5×1.5s poll all lost the race against
langgraph dev. That section now reports what was measured and recommends owning the label optimistically instead — no unverified fix ships in the post.Checks
apps/websiteblog spec passes (12/12)/blog/*and/docs/*links resolve to real slugs and filesAlso includes the design spec under
docs/superpowers/specs/.🤖 Generated with Claude Code