Add a CLI that agents can also use instead of the MCP

[BYK]

This CLI introduces commands like logs or errors which can also be
combined with a , or + to listen to multiple streams at once.

The first iteration will be a streaming log like tail -f but in the next
iteration we will add a no-follow mode that accepts some filters like a
timeWindow or limit as the MCP does.

Closes #958.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
spotlightjs	Skipped			Oct 10, 2025 7:23pm

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
spotlightjs	Building	Preview	Comment	Oct 9, 2025 3:15pm

[betegon]

250 new lines and 17 files modified but not a single comment from cursor 🥇. Having a look at this later today (I want to try it locally also)

edit: oh cursor took like 10 mins to leave a comment and there were no 👀 in the PR description...

[seer-by-sentry]

Potential bug: The code does not validate the result of envelope.getParsedEnvelope(), leading to a crash if the envelope is malformed (null) or empty (empty items array).

• Description: The function envelope.getParsedEnvelope() can return null if the envelope header is malformed. The code destructures this result via const { event } = envelope.getParsedEnvelope() without a null check, which will cause the process to crash. Additionally, even with a valid envelope, if it contains no items, the event[1] array will be empty. The subsequent access event[1][0][0].type will then cause a crash due to an out-of-bounds access. Both scenarios, a malformed header or a valid but empty envelope, will lead to a server crash.

• Suggested fix: Before destructuring or accessing properties, check if the return value of envelope.getParsedEnvelope() is null. Also, add a check to ensure the event[1] array (the envelope items) is not empty before attempting to access its elements. A guard clause like if (!envelope || !event || event[1].length === 0) { return; } would prevent both crashes.
  _{severity: 0.9, confidence: 0.95}

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[betegon]

First pass. Added a couple of commits to fix some bugs. I'll do another review later.

I tried it locally, it's great and we need to improve the formatter 😆 .