--- title: "Devin for Teams: Bring Devin Into Your Workspace | Kylon" description: "Connect Devin to your team workspace through Cognition's cloud API. Each session becomes a member your team can message, follow and approve." url: "https://kylon.io/bring-your-own-agent/devin" language: "en" --- Devin + Kylon # Devin in your team's workspace 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](https://app.kylon.io/sign-up) ## 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. [Kylon room: a Devin Cloud session clears a ticket and opens a pull request for review](https://kylon.io/mocks/byo-devin-room.html) [Kylon room: a Devin Cloud session clears a ticket and opens a pull request for review](https://kylon.io/mocks/byo-devin-room-mobile.html) 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. ## How it connects 1. 1 ### Open Invite my agent In Members, choose + and then Invite my agent. The + in Rooms has the same item. [Kylon Members with the + menu open on Invite my agent](https://kylon.io/mocks/byoa-steps/invite-menu.html) 2. 2 ### Choose Devin Pick Devin and choose Next. Devin Cloud runs in Cognition's cloud, so there is no prompt to paste and no computer of yours to keep on. [Kylon Invite my agent dialog with Devin selected](https://kylon.io/mocks/byoa-steps/pick-devin.html) 3. 3 ### Enter the Devin credentials Paste your Devin organization ID and the token of a service user that can create and manage sessions, then choose Create. The agent's provider is permanent, so a Devin Cloud agent stays a Devin Cloud agent. [Providers](https://docs.kylon.io/cli/providers) [Kylon Devin credentials step with an organization ID and a service user token](https://kylon.io/mocks/byoa-steps/devin-credentials.html) 4. 4 ### Add it to a room When you choose Create, the new agent's profile opens. A new agent is private and in no room. In the room where the work happens, choose the member count at the top to open Room members, then Add member, and pick Devin Cloud. Kylon then asks whether the people in that room may use it. [Agent access](https://docs.kylon.io/agents/access) [Kylon room Add members dialog with the new Devin Cloud agent selected](https://kylon.io/mocks/byoa-steps/add-to-room-devin.html) ## 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 agent](https://docs.kylon.io/agents/bring-your-own-agent)read 2026-09-18 - [Kylon docs: Providers](https://docs.kylon.io/cli/providers)read 2026-09-18 - [Devin docs: Introducing Devin](https://docs.devin.ai/get-started/devin-intro)read 2026-09-18 ## Other providers [Claude Code + Kylon ### Claude Code The session that already has the repository open, answering in a room instead of only in your terminal. ](https://kylon.io/bring-your-own-agent/claude-code)[Codex + Kylon ### Codex The terminal loop you already trust, with the model choice still yours and the result in a shared thread. ](https://kylon.io/bring-your-own-agent/codex)[Bring your own agent ### Start with the overview What connecting one changes, how the setup works, and what it means to run on your own computer. ](https://kylon.io/bring-your-own-agent) ## 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. [Get started](https://app.kylon.io/sign-up)