-
Notifications
You must be signed in to change notification settings - Fork 0
cowork routines managed agents
Nicolas Cravino edited this page Jul 29, 2026
·
1 revision
id: cowork-routines-managed-agents title: Cowork, Routines, and Managed Agents: Choosing the Right Layer for Agentic Work tags: [llm] category: agentic-frameworks published: 2026-07-29 created: 2026-07-29 updated: 2026-07-29 freshness: fresh date_source: git-commit source_file: Cowork-Routines-Managed-Agents.md
Anthropic's Cowork, Routines, and Managed Agents are layers, not alternatives: operator (no-code skills, local state, scheduling), developer (cloud execution, repo-driven), and platform (vaults, sandboxing, agent-as-product). Grounded in migrating year-old code-first newsletter pipelines to Cowork skills and running both in parallel.
- Decision framework — stop at the first yes: agent is the product → Managed Agents; repo/code-centric workflow → Routines; needs docs, Gmail, or persistent local state → Cowork; must run laptop-off → hybrid. [^src:articles-published §cowork-routines-managed-agents]
- The three cannot be consolidated today: Managed Agents has no scheduler, Routines has no credential vault, Cowork has no cloud execution — which is why the hybrid pattern exists. [^src:articles-published §cowork-routines-managed-agents]
- Rule of thumb: start in Cowork, prove value against a real baseline, and graduate to Routines or Managed Agents only when operational reality forces the shift. [^src:articles-published §cowork-routines-managed-agents]