Brian Lovin's multi-tasking pattern is two steps. First, tell your agent to keep all work organized in a Notion database and take detailed notes about progress and blockers on each page. Second, throw tasks into chat — manually, or automatically pulled from email, Sentry, or GitHub with routines — and most of the time those init a Cursor cloud session that starts building or fixing.

It's the best way he's found for one bot to work on many things at once while keeping visibility into what's flowing through the system, and the best way to resume an old task that got buried in a chat thread: ask the bot to find the right Notion page and get caught up. With the Notion MCP you don't do the setup by hand. Notion's own account quote-tweeted it.