Cursor Agent
3f19aaca39
Every client navigation in the observability UI blocked on two server round-trips before the destination page could render: 1. a lazy React Router `/__manifest` route-discovery request, and 2. a root-loader `.data` request that re-ran getPublicServerConfig() on every navigation even though the config is static for the server's lifetime. React Router keeps the previous page on screen until these resolve, so against a remote/cold dashboard backend the whole detail page appears to hang for seconds on each navigation. Ship the full route manifest on initial load (routeDiscovery: 'initial') and skip revalidating the root config loader on navigation (shouldRevalidate -> false). Measured against a throttled 150ms/1.5Mbps profile, home->run nav drops from ~339ms (two blocking round-trips) to ~23ms with zero blocking server requests; the page now renders immediately and only its own data loads afterward.
Workflow SDK
Getting Started
The Workflow SDK lets you easily add durability, reliability, and observability to async JavaScript. Build apps and AI agents that can suspend, resume, and maintain state with ease.
Visit https://workflow-sdk.dev to view the full documentation.
Community
The Workflow SDK community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects with other people.
Contributing
Contributions to Workflow SDK are welcome and highly appreciated. Please use GitHub issues and discussions to collaborate with the team and wider community.
Author list
Workflow SDK was built by engineers at Vercel and the Open Source Community.
The initial core contributing engineers are:
- Adrian Lam (@adriandlam)
- Dillon Mulroy (@dmmulroy)
- Gal Schlezinger (@Schniz)
- JJ Kasper (@ijjk)
- Nathan Rajlich (@TooTallNate)
- Peter Wielander (@VaguelySerious)
- Pranay Prakash (@pranaygp)
The Workflow SDK logo was designed by Cecilio Ruiz @ceciliorz
Security
If you believe you have found a security vulnerability in Workflow SDK, we encourage you to responsibly disclose this and not open a public issue.
To participate in our Open Source Software Bug Bounty program, please email responsible.disclosure@vercel.com. We will add you to the program and provide further instructions for submitting your report.