FOR AGENCIES THAT RUN MANY CLIENT SYSTEMS

CoachAven.
An agent per client project.

Open-source agent infrastructure for operators. Each project gets its own Claude Code sandbox with its repos and tools. Your team drives it from Slack, Teams or the web. The agent opens pull requests; your people merge. Run it yourself, or let us run it for you.

Slack · Teams · Web chat · GitHub · Open source, Apache-2.0
#project-atlas
MK
Mara14:02
@CoachAvenwhy do exports time out for large workspaces?
CA
CoachAvenApp14:03
The export job loads every row into memory before streaming. Above ~50k rows it exceeds the worker limit. I can page the query and stream in chunks — want a PR?
MK
Mara
yes please
CA
CoachAvenApp
Opened PR #482 — stream workspace exports in pages. Tests pass. Ready for review.
●checks passed · awaiting review · dan@team
What is CoachAven

The project is the unit.

Each client project gets its own sandbox, channel, tools, memory and cost line. One small process routes between them.

Sandbox

One sandbox per project

Each project gets its own container on a Docker host you run: its repos cloned, a persistent Claude Code process, a git worktree per task.

Chat

Slack, Teams or the web

One channel or room per project. Mention the bot and it answers in the thread, with the conversation kept. Teams and the web chat are in canary.

Review

Pull requests, people merge

Changes arrive as a branch and a pull request. Protect your default branch with required reviews, and GitHub enforces that people merge.

Schedule

Routines and reviews

Routines post briefs and reports into the project channel on a schedule. New pull requests get a review in the channel. A failing CI run gets a fix offered.

Sources

What the team reads

Optional per project: mail, chat, calendars and trackers go into a scrubbed store the agent queries. The sandbox never holds those credentials.

Messaging

Agents that ask each other

Optional: an agent can ask the agents of other projects or other installations. Between installations, messages travel end-to-end encrypted through a relay.

Ask a question. The agent reads the code and answers in the thread.
Ask for a change. The agent opens a pull request. Your developer reviews and merges.
How it works

Three steps.

It works with the chat, the repos and the tools you already have.

STEP 01

Connect chat and GitHub

Install the Slack app, or set up Teams or the web chat. Install the GitHub App on the repos.

STEP 02

Describe your projects

One config file: each project's repos, channel and tools. Grafana, Sentry, your ticket tracker, a read-only database: over MCP, per project.

STEP 03

Work in the channel

Mention @CoachAven in a project channel. It answers, investigates and opens pull requests. Your developers review and merge.

Your chat
Slack, Teams or web

One channel or room per project. Ask in a thread, get an answer or a pull request back.

Control plane
One small process

Routes messages, holds the long-lived credentials, runs the schedule, scrubs secrets. Makes no model calls itself.

Sandbox per project
Claude Code + your repos

A container on a Docker host you run. Clones the repos, runs builds and tests, opens PRs, reaches your tools over MCP.

Open source

Run it yourself. Or let us.

The whole thing is Apache-2.0: one Node process, a Docker host for the sandboxes, your chat and your GitHub.

Self-host it

  1. 01Create the Slack app from the manifest in the repo.
  2. 02Pick a sandbox host: a Docker host you own, or the same machine. Build the sandbox image and push it to your registry.
  3. 03Install the GitHub App on your org. Add a Claude Code token (claude setup-token).
  4. 04List your projects: repos, channel, tools. One file.
  5. 05npm run orch -- slack. Mention @CoachAven in the project's channel.

Model credit: a Claude subscription token is the quick way to try it. For a team or clients, API-key credit is coming.

Or we run it for you

We install CoachAven for your team — your Slack or Teams, 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
Built to be trusted

Where the limits sit.

The design decides what the agent can reach. Where a limit is only a prompt rule, we say so.

The sandbox is the boundary

The model runs inside an isolated sandbox per project. The control plane that talks to your chat 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. The bot's own keys (GitHub App key, chat tokens, gateway and source credentials) never enter a sandbox.

Secrets stop before the model

Every message and every ingested document is scrubbed of secret-shaped strings before it reaches the agent.

Pull requests, not pushes

Changes arrive as pull requests on a branch. That is a rule in the prompt; with required reviews on your default branch, GitHub enforces it.

The team

One builder.
Ships daily.

You talk to the engineer building CoachAven, not a sales desk.

Ivan Adutskevich
Ivan Adutskevich
Lead Developer

CTO / Lead developer. 18+ years shipping software. Builds CoachAven, runs it for the first teams, answers the issues on GitHub.

LinkedIn
Get in contact

Want to see CoachAven working?

Tell us what you run. We'll show you what your first agent looks like.

ivan@coachaven.com
Your details only get used to set up this call.