Twenty vs Woodpecker

Twenty ships twice weekly across two tags, `twenty/` for the application and `sdk/` for the developer surface, and the last month put most of its weight on AI. A Slack conversational assistant, AI agent nodes in the workflow engine with pinned models, and a lazy tool-loading path for open-ended agent runs all landed in late July. In parallel the app platform keeps hardening: apps can enqueue jobs onto workers, OAuth authorizations are recorded and enforced per user, and web auth moved from localStorage token pairs to httpOnly cookie sessions.

The CRM is becoming a host for agents rather than a system agents call into. Pinning a concrete model on an agent node, excluding interactive tools from unattended workflow runs, and returning agent failures as result errors are the details of a team building an execution environment they expect to run without supervision. The application and marketplace work points the same direction, which is why install commands, per-user authorization records and licensing policy keep recurring in the notes.

Expect the Slack assistant to extend to other channels, and the AI agent node to gain the permission scoping the OAuth authorization work is building toward, since an agent running unattended inside a workspace is the obvious next thing to constrain.