Features
Everything Hinzel does today, grouped by what it is for.
Request accessSet up and change agents by talking to them.
Describe it in chat
Tell Hinzel's assistant what you want in Slack or web chat. It writes the rules for you.
Starters
Begin from triage, root-cause analysis, code generation or a daily digest.
Drafts and diffs
Every change is a draft, with a diff against what is live now.
Tests and replays
Run behaviour tests and replay past events before anything ships.
Approval to publish
A project admin approves each change before it goes live.
Edits from a conversation
Say "add this to our instructions" in web chat, and the project updates itself after approval.
Deterministic rules decide when agents start and what they may do.
Event triggers
Start or continue a run on the exact events you describe.
Schedules
Cron schedules that follow business hours, time zones and holidays.
Multi-step rules
Track an issue through its states, with timers such as "2 business hours without a reply".
Actions without an agent
Post a message, call an action or update a record straight from a rule.
Records
Typed project data that rules, agents and people can change, with a full history.
Watches
"Ping me when this PR merges" sets a watch from inside a conversation.
Agents work where your team already talks.
Replies in the thread
Answers land in the Slack thread, Jira issue, Zendesk ticket or pull request that asked.
Web chat
Chat with an agent in the console, with its files, artifacts and subagents beside the thread.
Live view
Watch each step of a run as it happens.
Stop at any time
Stop a turn from the console, a Slack shortcut or a text command.
Questions for a person
An agent can ask a question and wait for the answer before it continues.
Attachments
Files shared in a conversation reach the agent, and its outputs come back as attachments.
Agents that work in your repos like a teammate.
A branch for every run
Each code run works on its own branch in its own workspace.
Pull requests
Agents open pull requests and follow the reviews on them.
More than one repo
Check out other repos into a run and open pull requests from each of them.
CI events
Start work when a check suite or workflow run finishes.
Sandboxes
Run builds and tests in an isolated sandbox, apart from the host.
Every project on its own terms, under one org policy.
Project scopes
Each project reaches only the connections it is given.
Roles
Org owners and admins, project admins and members, each with clear rights.
Approvals
Sensitive actions wait for one click in Slack or the console.
Personal accounts
Agents act as the person who asked, with that person’s own connected account.
Budgets
Spend limits for each project.
Traced end to end
Follow any reply back to the event that caused it.
Agents that share their work with each other and with you.
Agent to agent
Projects hand work to each other, with a hop limit set by the org.
Artifacts
Reports and files are versioned, with a record of where each came from.
Project memory
Facts the team pins or a run learns, each with its source.
Plugins
Pin skills and tools per project, from your org or a public marketplace.
See what agents cost and keep data only as long as you need.
Usage
Tokens and cost for each project, run and model.
Feedback
Reactions and console buttons record how people judged each reply.
Retention
Each kind of data has a retention period, and orgs can lengthen some of them.
Erasure
Remove one person from every store on request.
Offboarding
Close an org and delete its data in one recorded process.
Put a fleet to work this week.
Hinzel is in early access. Tell us about your team and we will set up your first project with you.