Skip to main content

dev-agents

An AI agent that lives in Slack and gives your whole team developer-like access to the codebase.

Open source (MIT) · Self-hosted · Your data stays yours · Deploy in 5 minutes


Deploy Now · Quick Start · Docs · Website

License Python Docker Build Status Code Quality


Your developers use Copilot to write code. But what about everyone else on the team?

Product owners need to understand what changed. QA needs test plans from pull requests. Support needs to trace bugs back to code. DevOps needs to analyze incidents. They all end up interrupting developers or waiting.

dev-agents connects to your repos, issue trackers, and logs, and makes all of it accessible through Slack. Anyone on the team can ask questions in plain English. No IDE required. No code skills needed.

"What used to take days now happens automatically." — CTO at a 50-user medical SaaS company using dev-agents daily across engineering, product, and support teams

What it does

Your team asks questions about the codebase in Slack — in plain English. No IDE, no git clone, no code skills needed.

@DevAgents how does the authentication flow work?
@DevAgents what changed in the payment module this sprint?
@DevAgents which files handle the webhook retry logic?
@DevAgents what's the difference between OrderService and OrderProcessor?

Code research is the core skill: anyone on the team can ask about architecture, recent changes, dependencies, or how a feature works and get an answer grounded in the actual code, not stale docs.

Hosted plans at codeligence.com add maintained skills for test plans, release notes, code review, story refinement, and log analysis.

Quick start

Option 1: Docker (recommended)

# 1. Download config
wget -O .env https://raw.githubusercontent.com/codeligence/dev-agents/main/.env.example

# 2. Edit .env — add your Slack token, git provider, and LLM API key

# 3. Run (mount your cloned repo into the container)
docker run --rm -it --env-file=.env \
  -v /path/to/your/repo:/code \
  codeligence/dev-agents

Or use the Setup Wizard to generate your config interactively.

Option 2: From source

git clone https://github.com/codeligence/dev-agents.git
cd dev-agents
cp .env.example .env    # then edit .env
pip install -e .[all]
python -m entrypoints.main

Then in Slack:

@DevAgents how does the authentication flow work?

Why teams choose dev-agents

Your infrastructure, your data. Runs in your cloud or on-prem. No data leaves your environment. You bring your own LLM API keys. Your code and your team's questions stay on your infrastructure.

Works where your team already works. Slack and Teams. No new tool to adopt. No IDE needed. Your QA lead, product owner, and support team can use it on day one.

Open source (MIT). Full source code on GitHub. Your security team can audit everything. No copyleft restrictions, no procurement delays. Use it however you want.

Any LLM provider. Anthropic, OpenAI, Google, Azure, or run local models. Switch providers anytime without changing workflows.

Multi-repo. Connects to multiple repositories at once. Ask questions that span your entire codebase.

Extensible. Add custom skills for your team's specific workflows. Build on what's there or create something new.

Integrations

Category Supported
Chat Slack, Teams
Git providers GitHub, GitLab, Azure DevOps, Bitbucket
Issue trackers Jira, GitHub Issues, GitLab Issues
Logs ELK, Loki, log files
LLM providers All major providerers + local models
Protocols MCP, AG-UI, A2A

Who it's for

The whole team — not just developers.

  • QA leads tired of spending hours writing test plans from pull requests
  • Product owners who need code-level answers but can't read code
  • Support engineers tracing customer bugs without knowing the codebase
  • DevOps teams analyzing incidents and deployment failures
  • Engineering managers who need visibility without interrupting developers
  • CTOs looking to give the whole team self-service access to project knowledge

Works best with teams of 10-200 on active, evolving codebases where documentation, testing, and cross-team communication matter.

Self-hosted by design

Most AI dev tools are SaaS. Your code goes to their servers. Your questions go through their infrastructure.

dev-agents deploys to your cloud - AWS, Azure, GCP - or on-prem. You own the infrastructure. You control the data. You bring your own LLM keys and pay providers directly. No per-seat pricing surprises.

If your team already self-hosts GitLab, Jira, or other dev tools, you already believe in owning your infrastructure. This is the same philosophy applied to AI.

Commercial support

Need an admin dashboard, team analytics, SSO, or dedicated support? See codeligence.com for plans starting at $59/month — or book a demo.

Community

License

MIT. Use it, fork it, deploy it, sell it. No restrictions.

Metadata

Release files for dev-agents 1.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dev-agents 1.3.1
File Size Uploaded
dev_agents-1.3.1.tar.gz 215.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dev-agents 1.3.1
File Interpreter ABI Platform
dev_agents-1.3.1-py3-none-any.whl Python 3 none any Details

Total release size: 479.9 kB

Release files / dev_agents-1.3.1.tar.gz

Download URL dev_agents-1.3.1.tar.gz
Size 215.1 kB
Tags Source
SHA-256 checksum
How to use checksums
17c6bee9b29dbe7fc4c1bd6aa535d94402db7d3930d7d49ae6d17a9aae9e6ae1
BLAKE2b-256 checksum
How to use checksums
d616fc7521dbcc7c54d0742e89ae3a422a513a18ae6179d84575ead973b14a9e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Release files / dev_agents-1.3.1-py3-none-any.whl

Download URL dev_agents-1.3.1-py3-none-any.whl
Size 264.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f99aaa1ce66eb15b67b8e50d5a8f45cdc19b7e94a2205bbcd5c59fcca804b01a
BLAKE2b-256 checksum
How to use checksums
ba61e0298a477426e3103d4ec37e51f09d28b66605854d9b12319f6de991dab3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Release history Release notifications | RSS feed

This release

1.3.1 This release

2 release files

1.3.0

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.3

2 release files

1.0.2

2 release files

1.0.1

2 release files

1.0.0

2 release files

0.10.0

2 release files

0.9.3

2 release files

0.9.2

2 release files

0.9.1

2 release files

0.9.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page