Claude CoworkFirst met in aicp-c3-basecamp-04 · Coding agents & editors · Automation platforms
Claude's desktop workspace for file and task work — described in the course as a UI wrapper over Claude Code.
The work is on your own machine, needs judgement rather than a fixed pipeline, and you'll be present for it.
Runs recurring scheduled tasks without you building a workflow
Full file access plus a sandboxed shell in one place
No workflow to author — you describe the task instead of drawing it
Works directly on local files with an agent
Runs scheduled recurring tasks
Handles open-ended work that has no fixed node graph
Doesn't survive your laptop closing — the BC4 criticism, and the reason n8n exists
Doesn't expose the workflow as a portable artifact the way n8n JSON does
Isn't open source
Judgement-heavy local work — exactly this KB pipeline. n8n is the answer for always-on, deterministic plumbing.
Coding agents & editors · Automation platforms
It is the environment every extraction sitting runs in.
The BC4 critique is fair and worth heeding: anything in this pipeline that must run unattended (nightly archive checks) is a candidate to move to n8n, while the extraction itself is exactly the judgement work Cowork is for.
current
n8n: BC4's explicit comparison: laptop-bound and flexible vs always-on and purpose-built
claude-code: 'a UI wrapper on Claude Code' per the trainer