⌘K
Mike Tickstem **Update:** Tickstem now includes **status pages** that auto-generate from your uptime monitors and heartbeat checks --- no manual ***"we're investigating"*** posts needed. The page reflects your actual monitor state in real time. If your monitors are green, the page is green. If an endpoint goes down, the page updates automatically. You get a public URL at `https://tickstem.dev/status/your-slug` --- shareable with users, **no separate service needed**. Works well alongside Vercel deployments: monitor your API routes, set up a heartbeat on your background jobs, and your status page stays current without any manual updates. Free tier includes 5 monitors and a status page. https://tickstem.dev
Mike Tickstem **Update:** Tickstem now has an **MCP server** --- if you use Claude Code or Cursor alongside your Vercel projects, your AI assistant can register cron jobs, create uptime monitors, and set up heartbeat checks directly from the editor. **Remote option (no install)**: connect via https://mcp.tickstem.dev/mcp --- works with any MCP-compatible client. **Local binary option**: go install github.com/tickstem/mcp/cmd/tsk-mcp@latest Same API key you're already using. Useful when you're scaffolding a new Vercel project and want the agent to wire up monitoring as part of the build.
Hello, for the past week and a half, I haven't been able to add or edit the names of new files or existing files in the Vercel VO editor. Clicking with the mouse no longer works. What should I do? When will this issue be resolved? Thank you....
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0
Mathieucrcs @amyegan/ @pawlean / @ty37zhang can you help me please ?
Ty Zhang @mathieucrcs This will be added back today.
Pauline P. Narvas Is your application client-side rendered static site? Static site requests don’t appear in runtime, only function invocations do. This is expected behavior for React apps without server-side functionality.
ADALIGO If your React app is purely client-side rendered (CSR) or a static site, this is expected. Vercel runtime logs only capture **server-side invocations**, like API routes or serverless functions. Static pages served by React won’t appear in runtime logs, even if traffic is coming in. A couple of things you could check: * Are you using **Next.js** with any server-side functions or API routes? Those logs will show. * If not, you’d need to route logging through a serverless function to capture requests in Vercel logs.
