Warp is a fast agentic terminal, and it can share a live session from a host's machine. Coshell is a different shape: a *neutral cloud session* the whole team owns and works in together, with one agent.
Warp shares one developer's session, running on their machine.
Coshell puts the whole team in one neutral cloud session with one agent.
Overview is in with the three stat cards and the recent orders table. Live on http://localhost:5173.
Cards stretch now. The grid uses align-items: stretch and each delta line is pinned to the bottom with margin-top: auto.
Added the toggle. 30 days aggregates by week and the axis relabels. 8 tests pass.
Delta sits on the top row now, right aligned, so the numbers line up down the column.
Token bucket middleware is in with 12 tests. Step 1 verified.
Moved the bucket to Redis with a Lua script so the check is atomic across replicas. 14 passing. Steps 2 and 3 verified.
Webhooks now share the limiter. 16 passing. Marking step 4 verified and moving to the flag rollout.
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?
Understood, Node 22 LTS from NodeSource.
Server is running at http://localhost:5173/, Vite dev server ready in 284ms.
Eight commits since main: the coupon model, the checkout hook, and a migration. No PR yet.
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.
Drafted docs/plans/discounts.md with five steps. It is waiting for approval in the Plan tab.
Hi. Big Pickle here, ready when you are.
2, 3, 5, 7, 11, 13, 17, 19, 23, 29.
1
2
3
4
5
6
7
8
9
10
11
12
bun test after every step, load test before the flag movesProtect /v2 from bursty API keys without slowing normal traffic. One key should never be able to starve the others.
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.
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%.
Overview is in with the three stat cards and the recent orders table. Live on http://localhost:5173.
Cards stretch now. The grid uses align-items: stretch and each delta line is pinned to the bottom with margin-top: auto.
Added the toggle. 30 days aggregates by week and the axis relabels. 8 tests pass.
Delta sits on the top row now, right aligned, so the numbers line up down the column.
Token bucket middleware is in with 12 tests. Step 1 verified.
Moved the bucket to Redis with a Lua script so the check is atomic across replicas. 14 passing. Steps 2 and 3 verified.
Webhooks now share the limiter. 16 passing. Marking step 4 verified and moving to the flag rollout.
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?
Understood, Node 22 LTS from NodeSource.
Server is running at http://localhost:5173/, Vite dev server ready in 284ms.
Eight commits since main: the coupon model, the checkout hook, and a migration. No PR yet.
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.
Drafted docs/plans/discounts.md with five steps. It is waiting for approval in the Plan tab.
Hi. Big Pickle here, ready when you are.
2, 3, 5, 7, 11, 13, 17, 19, 23, 29.
1
2
3
4
5
6
7
8
9
10
11
12
Not a terminal per developer, and not a session anchored to one machine. A neutral cloud session the team shares, with one agent. Every line below is running in production today.
In Warp, a host shares their own session, running on their machine, and others operate it remotely. In Coshell the session lives in a cloud drive the team owns, so no laptop has to stay on and everyone is a first-class participant in the same running environment.
Warp is priced per user with metered AI credits. Coshell is free to self-host, no seats: run a drive on your own machine, your whole team in your org, unmetered, and no per-seat charge.
A drive stays warm in the cloud with your files, terminal, and an integrated browser preview, reachable from any browser or the CLI. There is nothing to install and no host session to keep alive for teammates to work.
Coshell runs 70+ models on your own provider keys, scoped per drive, billed by your provider. It is built on OpenCode, which, fittingly, is also one of the agent harnesses Warp can run.
| Warp | Coshell | |
|---|---|---|
| What it is | A fast agentic terminal and dev environment, per developer | A shared cloud session a whole team works in with one agent |
| Where the session runs | On the host's machine; cloud agents orchestrate in the background | In a team-owned cloud drive: shared filesystem, terminal, browser preview |
| Live collaboration | Host shares their session; others view or run commands | Everyone joins one neutral session and prompts one agent together |
| Anchored to | The host developer's machine | A team-owned drive, no laptop dependency |
| Pricing basis | Per user, plus metered AI credits | Free to self-host, no seats |
| Team size | Priced per user | Your whole team, one drive |
| Models | Bring your own key; multiple agent harnesses | Bring your own keys, 70+ models, built on OpenCode |
| Where you work | A terminal app on your machine | Any browser, or the CLI, nothing to install |
| Best for | A best-in-class agentic terminal per developer | A team working with one agent in one shared session |
Many engineers keep a fast terminal for their own work and join a shared Coshell drive when the work is shared. Coshell runs your own repo on your own model keys, pushes to your real git, and is free to self-host, so the whole team can be in one session without a per-head bill.
It does, and it is good. The difference is architecture. In Warp, one person hosts their session, running on their own machine, and grants others view or edit access, so collaborators operate the host's environment remotely. In Coshell the session lives in a cloud drive the team owns, so there is no host machine to depend on, everyone is a first-class participant in the same persistent environment, and there are no seats to buy.
Yes. Many engineers keep a fast terminal like Warp for their own work and join a shared Coshell drive when the work is shared: pairing, debugging together, onboarding, live review. Coshell is built on OpenCode, which Warp can also run as an agent harness, so they sit comfortably in the same toolbox.
Warp is priced per user with metered AI credits, so cost scales with headcount and usage. 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 on either, billed by your provider.
Yes. Coshell runs 70+ models on your own keys, scoped per drive, and a drive pushes to your real git as ordinary git. Self-host it on your own machine and your code never leaves it, free; the Enterprise tier adds org-wide on-prem, so your code never leaves your environment.
Keep your terminal for solo work. When the work is shared, open a drive and put the whole team in one neutral live session with one agent.