Devin works on its own. Coshell is a team working with one agent, live.

Devin is an autonomous AI engineer you delegate tasks to. Coshell is the opposite shape: a shared *live session* where your whole team and one agent build together, in the loop. Two different jobs, compared honestly.

Start free

Autonomous vs collaborative

Devin is autonomousYou assign Devin a task or a ticket, and it works on its own in its own cloud environment, then opens a pull request. For well-scoped, delegatable work it is a genuinely capable async engineer.

Coshell is collaborativeCoshell is the opposite shape: a whole team and one agent in a shared live session, building together in real time, with humans in the loop the whole way.

Different jobsThis is not better versus worse. It is delegate-and-review versus build-together. Many teams want both.

Devin takes a task and works on it on its own.

Coshell puts a team and one agent in the same live session, building together.

AOrders dashboard for acme-webARate limiter rolloutADev server on the VMDProject pending statusOCount to 120

Open

Orders dashboard for acme-web

feat/orders TRLF

Add the orders overview to the dashboard: revenue today, order count, and average order value, then the recent orders table.Priya Nair

Explored4 reads

EditOrdersDashboard.jsx /src/pages/+77−0

Editindex.css /src/+33−0

Overview is in with the three stat cards and the recent orders table. Live on http://localhost:5173.

2 Changed files+110 −0

src/pages/OrdersDashboard.jsx+77−0

src/index.css+33−0

Can the stat cards stretch to equal height? The average order card is shorter than the others.Lena Fischer

Editindex.css /src/+4−1

Cards stretch now. The grid uses align-items: stretch and each delta line is pinned to the bottom with margin-top: auto.

Add a 7 day / 30 day toggle above the chart. Default to 7 days.Tom Reyes

EditOrdersDashboard.jsx /src/pages/+31−4

Shellbun test

Added the toggle. 30 days aggregates by week and the axis relabels. 8 tests pass.

Move the delta onto the card’s top row, right aligned against the label.Priya Nair

Editindex.css /src/+6−2

Delta sits on the top row now, right aligned, so the numbers line up down the column.

Use var(--brand) for the Export button, not a hardcoded hex.Tom Reyes

EditOrdersDashboard.jsx /src/pages/+1−1

1 prompt queuedClear queue

Lena FischerMake the Refunded pill amber. Red reads like an error.

Claude Sonnet 5

Rate limiter rollout

feat/rate-limit TR

Start the rate limiter plan. Token bucket per API key, 100 a minute.Priya Nair

Explored6 reads

EditrateLimit.ts /src/middleware/+64−0

Shellbun test

Token bucket middleware is in with 12 tests. Step 1 verified.

Keep the bucket in Redis, we run three replicas.Tom Reyes

EditrateLimit.ts /src/middleware/+22−9

Moved the bucket to Redis with a Lua script so the check is atomic across replicas. 14 passing. Steps 2 and 3 verified.

Execute step 4. Start with the webhooks route, I already reviewed the limiter.Lena Fischer

ReadrateLimit.ts

Editwebhooks.ts /src/routes/+14−2

Shellbun test

Webhooks now share the limiter. 16 passing. Marking step 4 verified and moving to the flag rollout.

Thinking

Claude Sonnet 5

Dev server on the VM

main TRLF

Start the dev server on this VM so the team can preview the orders dashboard.Priya Nair

Shellwhich node npm bun

Node.js isn’t installed on this VM, so I can’t start the dev server yet. I can install it with the system package manager and then run it. Want me to?

Yes, but use the LTS build, the API image pins Node 22.Lena Fischer

Understood, Node 22 LTS from NodeSource.

go ahead and install it and get the server started.Tom Reyes

Shellcat /etc/os-release 2>/dev/null | head -5; which apt-get

Shellsudo apt-get update -qq && sudo apt-get install -y -qq nodejs npm

Shellnode --version && npm --version

Shellnpm install

Shellnpm run dev &

Server is running at http://localhost:5173/, Vite dev server ready in 284ms.

Big Pickle

Project pending status

feature/discounts LFTR

What is the status of the discounts branch?Tom Reyes

Shellgit log --oneline feature/discounts -8

Eight commits since main: the coupon model, the checkout hook, and a migration. No PR yet.

Do we have a written plan for the discounts work?Priya Nair

No. You have no PLAN, TODO, or roadmap file.

Your closest thing to a plan is .coshell/review/dod.md: integer cents, handled promises, no focused tests, no dead exports.

Draft one from the commits and the dod file, then open it in the Plan tab.Lena Fischer

Readdod.md

Editdiscounts.md /docs/plans/+48−0

Drafted docs/plans/discounts.md with five steps. It is waiting for approval in the Plan tab.

Muse Spark 1.3 Free

Count to 120

main LFTR

Quick sanity check on Big Pickle before we let it near the repo. Say hi.Tom Reyes

Hi. Big Pickle here, ready when you are.

Without using any tools, list the first ten primes.Priya Nair

2, 3, 5, 7, 11, 13, 17, 19, 23, 29.

Without using any tools, count from 1 to 120, one number per line, then stop.Lena Fischer

1
2
3
4
5
6
7
8
9
10
11
12

Thinking

Big Pickle

Chat2PlanDeep ReviewBrowserReview

Morning. Plan is approved, I’m starting the orders dashboard on acme-web.8:52

Tom Reyes8:55I’ll take the limiter then. Which drive?

office-mac-mini has Redis running, use that one.8:55

Lena Fischer9:10Back online. Anything blocked?

Tom Reyes9:11Nope. OrdersDashboard.jsx is Priya’s, limiter is mine, webhooks are free if you want them

Lena Fischer9:12Taking webhooks.

Lena the Refunded pill should be amber, not red. I queued a prompt for it9:30

Tom Reyes9:41Picking up rateLimit.ts for the webhooks route

Lena Fischer9:42Tom I already touched the 429 path there, check the overlap note before you push

Step 4 in the plan is mine, I’ll ping when the tests are green

Sounds good. I’ll review after, then we roll the flag.9:44

Rate limiter rolloutDetailsWorking

Spec approvedPlan approvedExecuting 3/5

Goal

Protect /v2 from bursty API keys without slowing normal traffic. One key should never be able to starve the others.

Approach

A token bucket per API key, 100 requests per minute, stored in Redis so all three replicas share state. Over-limit requests get a 429 with a Retry-After header. Ship behind the rate_limit_v2 flag and roll out gradually.

Constraints

No new dependencies beyond ioredis, which we already run.
p99 latency budget: +2 ms on the hot path.
Existing tests stay green at every step.

Verification

bun test after every step. Load test with 1k keys before the flag moves to 50%. Watch 429 rate and p99 in the dashboard for a day at 10%.

Steps

Token bucket middleware with testsVerified

Add

Redis-backed bucket, atomic across replicasVerified

Add

Retry-After header on 429 responsesVerified

Add

Apply the limiter to /v2/webhooksLena, in progress

Add

Roll out behind the rate_limit_v2 flagWaiting

Add

on step 5, Roll out behind the flag

Priya Nair2m

Roll out to 10% of keys first, then 50%. Add both as substeps.

Lena Fischernow

Agreed, updating the step before the agent gets there.

Deep Review

feat/orders against main

Run review

No review yet. Run one when the branch is ready.

Port 5173Port...ShareInspect

acme

DashboardOrdersCustomersSettings

Orders

Last 7 days · updated just now

Revenue today$18,420+12% vs last week

Orders342+8%

Average order$53.86−3%

Revenue, last 7 days7 days30 days

MonTueWedThuFriSatSun

#10428Maya OseiPaid$128.40

#10427Theo LindqvistRefunded$64.00

#10426Ada MensahPaid$212.75

#10425Ravi ShankarPending$39.90

Tom

3 Changed files+112 −3

src/pages/OrdersDashboard.jsx+77−0

38 <div className="toolbar">

39+ <button className="btn">Filter</button>

40+ <button className="btn primary" style={{ background: '#5B4CF0' }}>

41+ Export

42 </div>

src/index.css+33−0

112+ .stat { border: 1px solid #e6e6e6; border-radius: 10px; }

113+ .stat .delta.up { color: var(--ok); }

114+ .status.refunded { background: var(--danger-bg); }

src/App.jsx+2−3

3- import { useMemo, useState } from 'react'

3+ import { useState } from 'react'

18- <Summary />

18+ <Summary />

19+ <OrdersDashboard />

Orders dashboard for acme-web

acme-vm

feat/orders

Add the orders overview to the dashboard: revenue today, order count, and average order value, then the recent orders table.Priya Nair

Explored4 reads

EditOrdersDashboard.jsx /src/pages/+77−0

Editindex.css /src/+33−0

Overview is in with the three stat cards and the recent orders table. Live on http://localhost:5173.

2 Changed files+110 −0

src/pages/OrdersDashboard.jsx+77−0

src/index.css+33−0

Can the stat cards stretch to equal height? The average order card is shorter than the others.Lena Fischer

Editindex.css /src/+4−1

Cards stretch now. The grid uses align-items: stretch and each delta line is pinned to the bottom with margin-top: auto.

Add a 7 day / 30 day toggle above the chart. Default to 7 days.Tom Reyes

EditOrdersDashboard.jsx /src/pages/+31−4

Shellbun test

Added the toggle. 30 days aggregates by week and the axis relabels. 8 tests pass.

Move the delta onto the card’s top row, right aligned against the label.Priya Nair

Editindex.css /src/+6−2

Delta sits on the top row now, right aligned, so the numbers line up down the column.

Use var(--brand) for the Export button, not a hardcoded hex.Tom Reyes

EditOrdersDashboard.jsx /src/pages/+1−1

Claude Sonnet 5

ChatPlanReviewDeep reviewBrowserTerminal

Rate limiter rollout

office-mac-mini

feat/rate-limit

Start the rate limiter plan. Token bucket per API key, 100 a minute.Priya Nair

Explored6 reads

EditrateLimit.ts /src/middleware/+64−0

Shellbun test

Token bucket middleware is in with 12 tests. Step 1 verified.

Keep the bucket in Redis, we run three replicas.Tom Reyes

EditrateLimit.ts /src/middleware/+22−9

Moved the bucket to Redis with a Lua script so the check is atomic across replicas. 14 passing. Steps 2 and 3 verified.

Execute step 4. Start with the webhooks route, I already reviewed the limiter.Lena Fischer

ReadrateLimit.ts

Editwebhooks.ts /src/routes/+14−2

Shellbun test

Webhooks now share the limiter. 16 passing. Marking step 4 verified and moving to the flag rollout.

Thinking

Claude Sonnet 5

ChatPlanReviewDeep reviewTerminal

Dev server on the VM

acme-vm

main

Start the dev server on this VM so the team can preview the orders dashboard.Priya Nair

Shellwhich node npm bun

Node.js isn’t installed on this VM, so I can’t start the dev server yet. I can install it with the system package manager and then run it. Want me to?

Yes, but use the LTS build, the API image pins Node 22.Lena Fischer

Understood, Node 22 LTS from NodeSource.

go ahead and install it and get the server started.Tom Reyes

Shellcat /etc/os-release 2>/dev/null | head -5; which apt-get

Shellsudo apt-get update -qq && sudo apt-get install -y -qq nodejs npm

Shellnode --version && npm --version

Shellnpm install

Shellnpm run dev &

Server is running at http://localhost:5173/, Vite dev server ready in 284ms.

Big Pickle

ChatPlanReviewDeep reviewBrowserTerminal

Project pending status

office-mac-mini

feature/discounts

What is the status of the discounts branch?Tom Reyes

Shellgit log --oneline feature/discounts -8

Eight commits since main: the coupon model, the checkout hook, and a migration. No PR yet.

Do we have a written plan for the discounts work?Priya Nair

No. You have no PLAN, TODO, or roadmap file.

Your closest thing to a plan is .coshell/review/dod.md: integer cents, handled promises, no focused tests, no dead exports.

Draft one from the commits and the dod file, then open it in the Plan tab.Lena Fischer

Readdod.md

Editdiscounts.md /docs/plans/+48−0

Drafted docs/plans/discounts.md with five steps. It is waiting for approval in the Plan tab.

Muse Spark 1.3 Free

ChatPlanReviewDeep reviewTerminal

Count to 120

acme-vm

main

Quick sanity check on Big Pickle before we let it near the repo. Say hi.Tom Reyes

Hi. Big Pickle here, ready when you are.

Without using any tools, list the first ten primes.Priya Nair

2, 3, 5, 7, 11, 13, 17, 19, 23, 29.

Without using any tools, count from 1 to 120, one number per line, then stop.Lena Fischer

1
2
3
4
5
6
7
8
9
10
11
12

Thinking

Big Pickle

ChatPlanReviewDeep reviewTerminal

What Coshell is for.

Not a more autonomous agent. The shared live session your team and one agent work in together, in real time. Every line below is running in production today.

A team co-drives one agent, live

With Devin you are at the bookends: scope the task, review the PR. In Coshell several people prompt one shared agent in one live session, steering and correcting it together as the work happens, on one running filesystem and terminal.

Multiplayer among humans, not many bots

Devin's parallelism is many agents, one per task. Coshell's is many people, your whole team on one drive, working with a single shared agent in the same session, with presence and follow so you can watch a teammate steer.

Predictable cost

Devin's cost scales with agent compute. Coshell is free to self-host, no seats: run a drive on your own machine, your whole team in your org, unmetered. Bring your own model keys across 70+ models, billed by your provider.

Runs your repo, pushes to your real git

A Coshell drive works in your existing codebase and pushes to your own repositories as ordinary git, so the work lands the way your reviewers expect. Live collaboration in the session feeds your normal pull-request flow rather than replacing it.

Coshell vs Devin, side by side.

	Devin	Coshell
Core shape	Autonomous agent you delegate a task to	Live shared session a team co-drives with one agent
Human role	At the bookends: assign the task, review the PR	In the loop throughout, steering the agent live
Collaboration	Many agents in parallel, one per task	Many people in one shared session with one agent
Pricing basis	Usage-based, scales with agent compute	Free to self-host, no seats
Team size	Priced by usage and seats	Your whole team, one drive
Models	Bundled model access by plan	Bring your own keys, 70+ models
Where code lives	Devin's own cloud environment, opens PRs to your repo	Your existing repo; pushes to your real git
Best for	Delegating well-scoped async tickets at scale	Building together with an agent, live

Also compare

WindsurfCursorClaude Code

Delegate to Devin. Build together on Coshell.

These are complementary, not competing. Hand Devin the well-scoped async tickets, and bring your team into a Coshell drive for the work that is better done together: pairing, live debugging, onboarding, review. Coshell runs your own repo on your own keys and pushes to your real git.

Use cases How multiplayer works Pricing, free to self-host

Built on OpenCode

Coshell vs Devin, answered

Is Coshell trying to be a more autonomous Devin?

No. They are different shapes of AI coding. Devin is autonomous and asynchronous: you delegate a task and it works on its own, then opens a pull request. Coshell is collaborative and synchronous: a team and one agent work together in a live session, with humans steering the whole time. Coshell's value is the live, in-the-loop collaboration, not running unattended.

When would I use Devin instead of Coshell?

When you have well-scoped, delegatable work you would rather hand off than do together: clear tickets, routine fixes, migrations you can review as a PR, or many independent tasks you want to run in parallel while you are away. That fire-and-forget, ticket-to-PR pattern is exactly what Devin is built for.

When is Coshell the better fit?

When the work is better done together than delegated: pairing on a feature, debugging a hard bug as a team, onboarding a new engineer, or reviewing the running app live. Coshell puts your whole team and one agent in the same live session, so the people who need to be in the room are in the room, in real time.

Can we use both Devin and Coshell?

Yes, and many teams would. Use Devin to delegate async tickets at scale, and use Coshell for the live, collaborative work: pairing, debugging together, onboarding, exploratory sessions. They are different jobs, and both push to your real git.

Build with your team, live.

Start free

Open a drive in the browser, or attach from the CLI. Put your whole team and one agent in the same live session, on the code you already have.