@vercel[bot]1mo ago
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| dashboard | Preview, Comment | Apr 17, 2026 1:15am |
Mirrors the settings API-keys UX across the playground config sidebar and getting-started page:
****-abcd + red Trash iconAlertDialog confirmation → immediate return to Generate statePreviously the "Composio-Playground" key was auto-created on first page load, shipped to the client on every `getApiKey` query, and masked client-side. Two problems:
This PR makes generation explicit and revocation actually stick.
🤖 Generated with Claude Code
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| dashboard | Preview, Comment | Apr 17, 2026 1:15am |
FAIL — Failed in 40s | PR Created | ComposioHQ/composio_dashboard
PR Browser Testing
Triage
Scan the PR diff. If it contains only non-renderable changes (docs, CI configs, README, scripts, type-only refactors, backend-only logic with no UI surface), return successfully with a one-line explanation. Otherwise, proceed.
Phase 1: Analyze
- Read the PR description and every changed file
- Identify every user-facing route, component, and interaction affected — including indirect effects (e.g., a shared component change ripples to multiple pages...
Insufficient credits