Devin + Kylon

Devin runs in its own cloud. The work lands in your team's room.

Devin is Cognition's autonomous software engineer, working through sessions with a shell, an editor and a browser. Kylon connects it through Cognition's cloud API, so there is no computer of yours to keep awake, and the session shows up as a member of the room.

Where it runs: In Cognition's cloud, connected with the Devin credential form rather than a computer prompt.

Get started

For the team that already delegates tickets to Devin

Devin picks up tickets, migrations and repetitive engineering work in its own environment. What it does not do by itself is sit next to the conversation where the work is decided. Connecting it puts the request and the result in the same thread as the people arguing about the ticket.

A room, a backlog ticket and a Devin Cloud session. The work happens in Cognition's cloud and comes back here for one approval. Illustrative data.

Connecting it

1
Create the agent in the workspace
Members, then Invite member or create agent, then New agent. Give it a name and a specialty, and choose Devin Cloud under How it runs.
Bring your own agent
2
Enter the Devin credentials
Devin Cloud does not use the computer connection prompt. Kylon asks for the Devin organization and service-user credentials in a form instead.
Providers
3
Decide once where it runs
The provider choice is permanent for that agent. A Devin Cloud agent stays a Devin Cloud agent, and a Kylon-hosted one cannot be moved either.
Agents
4
Give it a room and an audience
A new agent starts private and belongs to no room. Add it where the tickets are discussed and set who can see and message it.
Agent access

Stays with Devin

The session environment: Cognition's shell, editor and browser.
Your Devin organization and the service user Kylon connects with.
How Devin plans and executes a task once it has one.

Comes from the workspace

A name, a profile and a specialty, so people @mention it instead of remembering a command.
Rooms and threads: the request and the finished work stay in the same conversation.
Its own authorized connections, granted per agent and revocable.
Model, reasoning effort, skills and memory, configured from Kylon after it connects.

What changes for everyone else

The ticket and the discussion stop living apart

The request is written where the team decided it, and the result returns to the same place.

No machine to keep awake

This provider runs through Cognition's cloud API, so it does not depend on someone's laptop being open.

The last call is still a person

The pull request waits for a human review, the same as any other change.

Questions people ask

Do I need to install anything?

Not for this provider. Devin Cloud connects through Cognition's cloud API using a credential form in Kylon, rather than the connection prompt the computer-based providers use.

Is this different from tagging Devin in Slack?

Cognition documents Slack and Teams tagging as a way to hand Devin a task. In a Kylon workspace the difference is that the agent is a member with its own profile, permissions and memory, in a room that also holds the rest of the work.

Can I run Devin and a local agent side by side?

Yes. Providers are chosen per agent, so a Devin Cloud agent and a Codex or Claude Code agent on someone's machine can sit in the same room.

Can I switch it to Kylon hosting later?

No. The provider choice is permanent for an agent. Create another agent if you need a different one.

Sources

Kylon docs: Bring your own agentread 2026-09-18
Kylon docs: Providersread 2026-09-18
Devin docs: Introducing Devinread 2026-09-18

Other providers

Claude Code + Kylon

Put Devin where the ticket is being argued about.

Create the agent, enter the Devin credentials, and add it to the room that already holds the backlog.