A coding agent
in your Slack.
Aven joins your project channels, reads your GitHub, answers questions, and opens pull requests. Your team reviews and merges. Nothing ships without you. Open source — run it yourself, or let us run it for you.
One coach in four letters.
A Slack app that talks like a teammate and works like a developer.
Agent
Lives in your Slack channels. You mention it, it replies in the thread, it remembers the conversation.
Validator
Reads everything, changes nothing on its own. Every change is a pull request your team reviews; the agent never pushes to your main branch.
Engine
Runs Claude Code in an isolated sandbox per project, on your own hosts. Your repos never leave your infrastructure.
Navigator
Keeps the overview across projects. Sends digests, watches pull requests, follows CI.
Three steps.
Your code. Your data. Your rules. Aven fits in without moving anything.
Connect your systems
Install the Slack app. Give it the GitHub repos and the channels it should live in.
Plug in your sources
Grafana, Sentry, your ticket tracker, your databases — over MCP, per project. Aven answers with your data, not with guesses.
Launch in your channels
Mention Aven in a project channel. It answers, it investigates, it opens pull requests. Your developers still review and merge.
One channel per project. Mention Aven, get an answer or a pull request in the thread.
Routes messages, holds the credentials, scrubs secrets. Makes no model calls itself.
Isolated container on your host. Clones the repos, runs tests, opens PRs, reaches your tools over MCP.
Run it yourself. Or let us.
The whole agent is Apache-2.0: one Node process, one sandbox host, your Slack and your GitHub.
Self-host in an afternoon
- 01Create the Slack app from the manifest in the repo.
- 02Pick a sandbox host: a Docker box you own, or self-hosted Daytona.
- 03Install the GitHub App on your org, add a Claude Code token.
- 04List your projects: repos, channel, tools. One file.
- 05npm run orch -- slack. Mention Aven in a channel.
Or we run it for you
We install Aven for your team — your Slack, your GitHub, your own sandbox hosts — wire it to the tools you already have, write the first project prompts and keep it running. You get the agent and the person who built it; the code stays open, so there is nothing to be locked into.
- Installation and sandbox setup on your infrastructure
- Grafana, Sentry, ticket tracker and database connectors over MCP
- Project prompts, routines and digests tuned to your team
- Updates, monitoring and a direct line to the engineer
Four things it cannot do.
The design decides what the agent can reach — not a prompt asking it to behave.
The sandbox is the boundary
The model runs inside an isolated sandbox per project. The control plane that talks to Slack never calls a model itself.
Short-lived, scoped access
Each turn gets a GitHub token minted for that project's repos only, valid for an hour. Nothing org-wide ever enters a sandbox.
Secrets stop before the model
Every message and every ingested document is scrubbed for credentials before it reaches the agent — and again on the way out.
Pull requests, not pushes
Changes arrive as pull requests on a branch. Your reviewers and your CI decide what ships; the agent cannot.
One builder.
Ships daily.
You talk to the engineer building Aven, not a sales desk.
CTO / Lead developer. 18+ years shipping software. Builds Aven, runs it for the first teams, answers the issues on GitHub.
LinkedInWant to see Aven working?
Tell us what you run. We'll show you what your first agent looks like.
ivan@coachaven.com