Mochibrief

For software engineers

AI moves faster than you can read. Most of it doesn't apply to you.

Mochibrief ranks each development for your role and stack, explains why it matters to you, and gives you one concrete thing to try.

Build my feed →

Free · Four questions · Sign in with GitHub at the end

A real item, ranked

Today's top item for a backend engineer working with TypeScript and PostgreSQL. Yours ranks the same stories for your own answers.

Cursor Blog

Introducing the Agent SDK

What happened
Cursor made the Agent SDK behind its own agents, such as Bugbot, generally available. Agents are defined in code, respond to events like pull requests, and deploy to Cursor's infrastructure with agent-sdk deploy.
Why it matters
Team-specific review or compliance bots no longer have to be built from scratch or bent to fit someone else's product. Prompts, tools and evals sit in one versioned project, so an agent's behavior can be reviewed and tested like application code, and it can be self-hosted.
Why you should care · TypeScript
Tools are TypeScript functions and the agent is configured with a defineAgent call, so your editor, type checker and code review cover the agent the same way they cover the rest of your codebase.
Try this
Create a project with defineAgent from @cursor/agent-sdk, write one Markdown prompt that checks pull requests against a single team rule, and test it in the local playground with an eval before using agent-sdk deploy.
Why this is here
  • You use TypeScript
  • Core to Backend work

How it works

  1. 01

    Discover

    Real developments from vendor blogs, changelogs, security advisories and reporting. Every one is linked to its source.

  2. 02

    Understand

    What happened, why it matters, and why it matters to you: a paragraph written for your role or your stack.

  3. 03

    Apply

    Every item ends with one concrete thing to try, small enough to fit in under an hour.

Not another newsletter

Ranked for you
Your role, stack and goals set the order. A devops engineer and a frontend engineer see the same week differently.
Reasons shown
Every item says why it is in your feed: your stack, your role, your goals, or that it is new.
One thing to try
Each item ends with an action you can take today, not another link to read later.
Sources first
We quote at most a short excerpt and always link the original. The commentary is ours; the reporting is theirs.

Build your feed in four answers.

Build my feed →