Target systems & plugins

Target systems are the systems agents work in — ticket systems, code hosting, mailboxes. They dock in as self-registering plugins, not hard-coded special cases.

The plugin pattern

Every target system brings a manifest: which actions it offers, which access it needs, how it wakes agents (trigger/webhook). New integrations are added without touching the core.

Available target systems

• Zammad — the first built-in: waking via trigger/webhook, REST actions, blocked ↔ pending, correlation via the ticket ID.
• GitLab — repository work: branches, merge requests, pipelines.
• Email / IMAP — mailboxes as a target system: read and answer mail.
• MCP — connecting tools via the Model Context Protocol.

Broker token instead of a permanent login

Access to a target system always goes through the secrets broker: short-lived and scoped to the task.