n8n just shipped a meaningful architecture change. The automation platform introduced an agent harness that lets agents operate as standalone objects, accessible across an entire instance or organization through native chat.
What Changed
Previously, agents in n8n lived inside workflows. The harness breaks them out. The new system adds:
- Native skill support
- Sub-agent orchestration
- Effort-based routing
- Persistent memory
- Text scheduling
- Chat connectors
Workflows still handle deterministic logic. Agents now use the MCP library for more dynamic tasks, which draws a cleaner line between rule-based automation and adaptive, context-dependent work.
Availability
The harness is in preview with a staged rollout planned for cloud users. No general availability date was announced.
For solo operators and small teams already running n8n, this is worth watching. Persistent memory and cross-instance access are the two features that could change how multi-step agent workflows get structured going forward.
