Integrations
A tik store is meant to be read by tools as readily as by people. Every
lens takes --edn or --format json, tik serve publishes
/tickets.edn and /explain/<id>.edn, and the frontier doubles as an
agent’s authorization boundary.
- Claude Code skill — install the plugin and Claude drives a store correctly, recording evidence rather than setting statuses.
- MCP server — the frontier as a gated tool surface over stdio.
- GitHub Actions
— failed workflow runs as
tickets, one per failure streak, with
tik statsfor per-repository metrics. - GitLab pipelines — failed pipelines as the same tickets, through an SSH port forward when the API only listens on its own host.
- Redmine — Redmine issues mirrored as tickets, with their history, so local work and remote tickets sit in one store.
- Odoo — Odoo project tasks mirrored as tickets, with their history from the chatter.