Atomic Agent
Customer story

How Atomic Agent handed integrations to Composio to scale a local-first agent

Valery B. · Atomic Agent

50+Distinct apps used through Composio
Distinct tools exercised through Composio
336
Model usage that runs on-device
65%
Atomic Agent

Atomic Agent is an open-source, local-first AI agent built by AtomicBot. It runs on the user's own machine, drives the browser, reads and edits files, runs approved shell commands, and remembers context across sessions. It already has daily users, including teams in health tech who cannot send client data to a cloud model and people running agents where there is no reliable internet at all. For those users an agent is only useful if the apps it touches keep working, so Atomic chose Composio to own that layer instead of turning it into a second product to maintain.

The problem

Every integration is something that can break

An agent that can only touch the local machine is limited. The jobs Atomic's users reach for most are email, then messaging, calendars, docs and project tools. Each of those is an integration someone has to build, authenticate, and then keep working as the outside services change.

The team did build two integrations themselves, Telegram and Discord. Doing the rest in-house would have meant owning their upkeep indefinitely: “building a lot of integrations on our own would just add another set of things that we need to look at, that we need to constantly update, check whether everything is working or not.”

The decision

Keeping integrations working became Composio's job

Atomic connects Composio over MCP, the same way it brings any tool into the agent. Composio keeps the integrations current and working, and the team spends its time on the agent harness, speed and the local-model experience.

As Valery put it: “you guys are doing this stuff, so we just delegate these tasks and we just have it on board.”

What changed

Breadth the team does not have to maintain

Through Composio, Atomic Agent has used 50+ apps and exercised 336 distinct tools, including Gmail, Google Drive, Calendar, Sheets and Docs, Trello, Jira, Confluence, Slack, Reddit and Telegram. None of that surface area sits on the Atomic team's maintenance list.

Email is the most common Composio-powered workflow, especially drafting and sending personalized emails and proposals at a volume that would be tedious by hand. Users have also taken the agent into settings the team did not predict, like a customer running Internet of Things workflows for his winery in a rural setting. The team saw a cost benefit too: “We definitely saved quite a bunch of tokens by using Composio instead of building all the integrations ourselves.”

What's next

Scaling on the same layer

Atomic describes itself as in a pre-scaling phase: a working agent with daily users and a roadmap focused on the harness, speed and growth. Composio is the integration layer it is scaling on, and the team's new weekly GAIA benchmark runs are the first to include Composio-provided tools.

Atomic Agent
Composio already covers a lot of our use cases, and just with one API key we can reach a lot of different services, which is what our team loves.
Valery B. · Atomic Agent
Put your agents to work

Power your agents with 1,000+ apps, in minutes.