Your coding agents,
on every computer.

A remote control you host yourself for Claude Code and Codex.
Chat, approve and ship from any browser or your phone.

Deploy to Cloudflare Star on GitHub

coderail.example.com

Studio Mac2 sessions1 needs you
Build boxcodex running
MacBook Airasleep · history kept

The whole computer,
from wherever you are.

CodeRail is the screen and keyboard of each machine, in a browser tab. Here is what that looks like.

01Chat
Pick a computer, pick an agent.
Claude Code and Codex sessions on every linked machine, in one sidebar. Plans, tool calls, model and effort stream in as they happen. Sessions you started in a terminal show up too.
coderail.example.com/m/studio-mac
Studio Mac
Search sessions
Needs you 1
npm test -- authFix the login redirect loop
webapp
Fix the login redirect loop
Add a dark mode toggle5h
api
Refactor billing webhookclosed
Fix the login redirect loop~/code/webapp
After signing in, users who came from /login?next=/login end up in a redirect loop. Can you fix it?
Plan2 of 3
Find where next is read after sign-in
Only allow same-site paths that aren’t /login
Run the auth tests
Search redirectAfterLogin
Read src/auth/redirect.ts
Found it. redirectAfterLogin trusts next as is. I’ll only accept same-site paths and never /login itself.
Edit src/auth/redirect.ts +3−1
Message Fix the login redirect loop
Ask before edits Opus 5.5 High
02Approve
Answer from wherever you are.
When an agent wants to run a command or edit a file, you get a push notification. Allow once, always allow, or deny, from the browser or your lock screen.
03Terminal
Real shells that keep running.
Terminals run on the computer itself, not in the tab. Close the laptop, open your phone, and the same shell is still there with its scrollback.
04Git
Read the diff before it ships.
Staged and unstaged changes, split or unified. Commit, pull and push on whichever machine has the code.
05Preview
Open the dev server, not a tunnel.
Browse the project’s files and open any local dev server through your own domain. Only people with access to that computer can see it.

coderail.example.com/m/studio-mac

Fix the login redirect loop~/code/webapp

After signing in, users who came from /login?next=/login end up in a redirect loop. Can you fix it?

Plan2 of 3

Find where next is read after sign-in

Only allow same-site paths that aren’t /login

Run the auth tests

Search redirectAfterLogin

Read src/auth/redirect.ts

Found it. redirectAfterLogin trusts next as is. I’ll only accept same-site paths and never /login itself.

Edit src/auth/redirect.ts +3−1

Message Fix the login redirect loop

Ask before edits Opus 5.5 High

Fix the login redirect loop

npm test -- auth

DenyAlways allowAllow once

9:41

Tuesday, October 27

CodeRailnow

Studio Mac needs you

Claude Code wants to run npm test -- auth

Allow onceAlways allowDeny

coderail.example.com/m/studio-mac/terminal

Terminal 1dev serverrunning 3h 12m · reattached

tomy@studio ~/code/webapp % npm test -- auth

> vitest run auth

✓ tests/auth.test.ts (6 tests) 412ms

✓ keeps same-site paths

✓ never sends you back to /login

✓ rejects //evil.example

Test Files 1 passed (1)

Tests 6 passed (6)

tomy@studio ~/code/webapp %

coderail.example.com/m/studio-mac/changes

fix/login-loop↑1PullPush

Msrc/auth/redirect.ts+3−1

Utests/auth.test.ts+24

1111export function redirectAfterLogin(next?: string) {

12- return next ?? '/'

12+ if (!next?.startsWith('/') || next.startsWith('//')) return '/'

13+ if (next.startsWith('/login')) return '/'

14+ return next

1315}

Only accept same-site next pathsCommit

coderail.example.com/m/studio-mac/preview/5173

localhost:5173/settings

AcmeDashboardBillingSettings

Settings

ThemeApplies on every device you sign in to.SystemLightDark

Email digestsA summary every Monday.

Two small programs.
Both of them yours.

A server in your Cloudflare account, and a bridge on each computer. Your browser talks to the server; the server talks to the bridges. Nothing else is involved.

Each computer

Studio MacmacOS

Build boxLinux

bridge

Your Cloudflare account

coderail.example.com

WorkerD1Durable Objects

You, anywhere

Any browsersigned in with your role

Your phoneapprovals by push

CodeRail Server

One-click deploy

One Cloudflare Worker, on your own domain.

Serves the web app and the API. Users and computers live in D1.
One Durable Object per computer relays traffic and keeps history while the machine sleeps.
Every request is checked against the caller’s role, and every change is audited.

Deploy to Cloudflare

CodeRail Bridge

macOS · Linux

A small background service on each machine.

Runs claude and codex through their official ACP adapters.
Serves terminals, files, git and dev-server previews.
Enforces folder limits on its own side, not just the server’s.

Install the bridge

No CodeRail account: There is no hosted service to sign up for. The server is yours.
Your keys stay put: Each machine runs claude and codex signed in as they already are.
No open ports: The bridge only dials out. No VPN, no port forwarding.
Apache 2.0: Read every line of it, fork it, run it however you like.

Ten minutes,
start to finish.

Deploy the Worker, create the first admin, link a machine. After that the bridge starts at login and reconnects on its own. You can check on it with coderail status, read coderail logs, or coderail unlink it.

Deploy to Cloudflare

coderail — zsh

Example session. Your domain and link code will differ.

Why we built it

Our agents run where the code is: a laptop, a desktop at home, a build box in the closet. They keep working when nobody is sitting in front of them.

The screen and keyboard didn’t come along. Every approval waited for someone to walk back to the right desk.

So we built a rail between them. You host it, it never holds your keys, and every computer fits in one tab.

Wiva, 2026

Put every computer you own in one tab.

Deploy to Cloudflare Star on GitHub

Your coding agents,on every computer.

The whole computer,from wherever you are.

Pick a computer, pick an agent.

Answer from wherever you are.

Real shells that keep running.

Read the diff before it ships.

Open the dev server, not a tunnel.

Two small programs.Both of them yours.