1. Say what you want
Describe the job in Slack or web chat.
Platform
How a message becomes finished work, and who checks it on the way.
Request accessSet up agents in plain words.
You describe what you want. Hinzel's own assistant writes the rules, checks them and asks for approval.
2. Hinzel drafts and tests it
It writes the rule, tests it and replays past events.
3. A person approves it
An admin reviews the change. Then it goes live.
-
Starters
Begin from triage, root-cause analysis, code generation or a daily digest, or from a blank project.
-
Checked piece by piece
Each edit is validated as it is made. Errors name the exact field that is wrong.
-
Tests and replays
Behaviour tests run on every draft, and a replay shows what the rule would have done last week.
-
A plain-English explanation
Every trigger comes with a description of what it does, generated from the rule itself.
-
Approval to publish
A project admin approves each change in Slack or the console. Open work finishes on the old version.
One event, end to end.
Every reply traces back to the event that caused it.
- 1
An event comes in
A Slack mention, a Jira issue, a webhook or a schedule. Each event is stored once, even when it arrives twice.
- 2
A trigger matches
The project's rules decide whether to start a run, continue one, or do nothing.
- 3
A run starts
It gets its own workspace and stays on the rules that were live when it started.
- 4
The agent works
Every tool call goes through the gateway, where it is checked and recorded.
- 5
The reply is delivered
It lands in the same thread or ticket, as the bot or as the person who asked.
- 6
The run follows up
A new message in the thread wakes the same run. Idle runs sleep and wake on the next message.
A deterministic engine.
Rules decide when agents start and what they may do. They run the same way every time.
Rules that remember
Follow a ticket through its states, with timers in business hours.
Records your agents keep
Typed data, with a history of who changed what.
-
Exact triggers
Conditions on typed event fields, checked before anything starts.
-
Actions without an agent
A rule can post a message, call an action or update a record on its own.
-
Calendars
Business hours, time zones and holidays for every timer and schedule.
-
Watches
"Ping me when this PR merges" sets a watch from inside a conversation.
Every call goes through the gateway.
Agents hold no credentials. They reach your tools only through the gateway.
-
Allow, ask or block
Each project's rules decide which actions run, which need a person and which never run.
-
The right identity
Actions run as the bot, or as the person who asked with their own connected account.
-
Budgets
Spend limits per project stop work before it goes over.
-
A record of every call
Each call is stored with its input, its result and the rule that allowed it.
A workspace for every run.
Each run gets its own place to work, and you can see everything it does.
-
Its own branch
Code runs work on a fresh branch of your repo and open pull requests from it.
-
Claude Code inside
Each run is a Claude Code session. Pick the model and pin the plugins per project.
-
Watch it live
Follow every step on the run page, and stop a turn from the console or Slack.
-
Ask a person
An agent can stop and ask a question, then continue when someone answers.
Connects to the tools you have.
Use the built-in connectors, add any MCP server, or send events in with a webhook.
Built-in connectors
Events come in and actions go out, with replies in the same thread.
Any MCP server
Add its URL. Its tools pass the same checks as every other call.
Webhooks in and out
A signed webhook starts a run. Outbound webhooks report the result.