The daily OS: calendar, Slack, email — before you open your laptop

The most advanced Cowork users don't start their day by opening their laptop and deciding what to do. Their setup has already done that for them.

JJ Englert, who runs Tenex and has documented his workflow extensively, has a Cowork task that runs at 6am every day. By the time he opens his laptop, it's already:

• Read his calendar for the day
• Pulled Slack notifications and categorised them as action/read/FYI
• Drafted replies to the emails that need responses, in his voice
• Reviewed what he shipped the day before
• Planned the current day's priorities

This is the daily OS pattern — using Cowork's scheduling and connector capabilities to build a morning briefing that runs automatically, assembles context from every relevant source, and delivers finished drafts instead of raw information.

It sounds like a lot. It's built one connector at a time.

How to build your version

Start with one connector, not five. The people who succeed with this pattern resist the temptation to wire up everything on day one.

Pick the single data source you most want in your morning briefing — calendar or email, for most people. Get the briefing working and useful for two weeks. Then add the next connector. The pattern compounds: each new source makes the briefing more complete, but each new source also introduces new failure modes. Adding them gradually means you're debugging one thing at a time.

The prompt structure for a minimal daily briefing:

"Read my calendar for today from Google Calendar. Identify: (1) any meeting that needs a prep note, (2) any conflict or gap worth flagging. Produce out/daily-brief.md with a Today's Priorities section, a Meetings section with one-line prep notes for each meeting, and a Flags section for anything that needs attention."

That's a useful briefing with one connector. When you add email or Slack, the briefing gets richer without the structure changing.

The /schedule command

Type /schedule in any Cowork task to convert it into a recurring job. A dialog walks you through the schedule — daily, weekly, specific days and times. Once configured, the task appears in the Scheduled sidebar in Claude Desktop, where you can pause, edit, or delete it.

The /schedule command is available on any task, not just elaborate automation. Schedule the simple ones too — a Friday afternoon competitive sweep, a monthly summary of your project notes. The scheduling overhead is minimal once you learn the pattern.

The laptop-awake limitation

This is the most important constraint to understand before you build anything: scheduled tasks only run while your computer is awake and Claude Desktop is open.

If your laptop is closed, suspended, or if Claude Desktop isn't running when a scheduled task fires, the task skips. It doesn't queue and run later. It skips.

This is not a bug. It's a design tradeoff: Cowork runs locally, not in the cloud, which means no cloud scheduler can reach it when the machine is off. The tradeoff is privacy and local execution — your files never leave your machine. The cost is that scheduled tasks require an awake host.

Three workarounds, in order of convenience:

Schedule during work hours. If your laptop is already open when the task fires, there's no problem. A 9am daily briefing is fine if you're at your desk by 9am. The 6am JJ Englert scenario requires a different approach.

Always-on desktop or mini-PC. A desktop machine that never sleeps, or a Mac mini / NUC, running Claude Desktop permanently. Task fires reliably because the machine never closes. Cost: the hardware you probably already own.

Cloud VM. An Azure B1s or B2s, an AWS t3.micro, a DigitalOcean droplet running Windows or macOS — approximately $10–15/month. Install Claude Desktop, configure your tasks, leave it running. This is the cleanest solution if you don't have an always-on machine, and the cost is low enough that most regular users find it worth it.

Building toward the full daily OS

The goal is a briefing that gives you a prioritised day before you've made a single decision. The connectors that matter most depend on where your work actually lives — but the common core is: calendar (what am I doing today), email or Slack (what needs my response), and a project status file (where is the work).

Start smaller than you think you need to. A briefing that reliably gives you today's meetings and three priorities is more valuable than an elaborate briefing that breaks every few days.