Can’t reach the server

Your sessions keep running. This page reconnects by itself when the network is back.

Coding Sessions

Your coding agents on your server

Sessions

 

CPU—
RAM—
DISK—

Install Coding Sessions

All quiet

No sessions running. Start one here,
then continue in its app or web terminal.

Start a session

Agent

Checking Codex support…

Open as

Branch

Choose Claude or Codex to enable Start.

Open old chat in Claude

Coding Sessions

Preferences

Agents & projects

Added to every new session name, so server work is easy to identify.

Connections & access

Server settings

Server & history

CLI updates

Keep Codex, Claude Code, and Command Code up to date on this server.

Runs daily at 06:00 Bangladesh time (00:00 UTC). Missed runs catch up when the server comes back online. Pausing the schedule does not stop an update already running.

Checking…

New sessions use the updated versions. Existing sessions are not restarted.

You're in

That link worked once and is now used up. Add a passkey so you can sign in from this device with Face ID, Touch ID or your device PIN.

Next: install agents in Settings → Agent authentication. Lost access later? Run sudo coding-sessions setup-link on the server.

Allow cs on to use this server?

It gets a CLI token with full control of your sessions. You can revoke it any time in Settings → CLI access.

Code . Allow only if you just ran cs yourself and your terminal shows the same code.

A session is asking for a secret

Server settings

Change how this server behaves without editing its configuration. A value changed here wins over the server's configuration until you reset it. Changes apply right away, no restart.

Checking…

App updates

Keep this server on the latest Coding Sessions release from GitHub.

Checks daily between 04:00 and 05:00 UTC. A new release is installed only if it starts cleanly; otherwise the current version is kept. Running agent sessions keep running through the restart.

Checking…

Agent authentication

View and manage the accounts used by agents on this server.

Agent

Account
Plan
Organization
Signed in since

Choose an agent to see its account. Changes apply to the server account; existing sessions may need to sign in again.


  
Installs as this server's account, never as root; agents that come from npm need Node.js 22 or newer. Third-party tools with their own accounts and terms — sign in above, or for presets in Settings → Commands.

  





  

  
Sign in to Claude

  
If sessions fail to start because the server's Claude login expired, redo it here.

  Open login page
  
Starting…

  

    
    
  

  

  
  





  

  
Sign in to Codex

  
Authorize the Codex CLI used by sessions on this server. Credentials never pass through this page.

  

    
Starting device sign-in…

    

      Device code
      
    

  

  Open verification page
  
  
  
  





  

  
GitHub access

  
Paste a personal access token so sessions can use gh and push over https. The token is stored by the GitHub CLI on the server — never in this app.

  
Checking…

  

    
    
Create one at github.com → Settings → Developer settings → Personal access tokens (scopes: repo, read:org, workflow).

    
  

  
  





  

  
Claude.ai browser

  
A signed-in browser on the server deletes chats from Claude when you ask for it while ending a session. Sign in again if deletions start failing.

  

  

  
  

  

    
    
  

  

    The server browser's screen
    
Tap to click. Drag to move a piece. The picture updates every second.

  

  
  





  

  
Projects

  
Sessions can only start inside these folders.

  

  

    
    
    
    
  






  

  
Commands

  
Add another CLI agent and it joins Claude, Codex and Command Code in the agent picker, with a managed session, a web terminal and history. Presets also connect the agent to Coding Sessions over MCP and follow the server's permission mode. Commands have no remote control, chat link, or conversation resume.

  
  

  
Third-party tools from their own vendors, with their own accounts and terms. What each preset sets up

  
  

  

    
    
    
    
    
  

  





  

  
Secrets

  
API tokens and keys every new session receives as environment variables. Values are encrypted on the server and never shown again. Running sessions keep the values they started with.

  

  
Stored here

  

  

    
    
    
  

  
From a secret manager

  
Connect a vault and its secrets join every new session. Rotated values are picked up within five minutes; if the manager is unreachable, the last values fetched are used. A secret stored here wins over one with the same name from a manager.

  

  

    
    
    

      
      
      
Needs the bws CLI on the server. Use a machine account access token.

    

    

      
      
      
      
      
      
Uses Universal Auth. Paste the identity's client secret below.

    

    

      
      
      
      
      
Reads one KV v2 secret; each key becomes a variable. Use a token whose policy can only read that path.

    

    
    
  

  





  

  
Agent token

  

  

    
    
  

  
  





  

  
Connect Claude or Codex

  
Each app signs in once with your passkey and an Allow, then drives your sessions as tools. Only press Allow right after you started the connection yourself.


  

    
    

      

      Copy
    

    
Settings → Connectors → Add custom connector, paste the URL, leave the OAuth fields empty. One connector covers all three apps.

  


  

    
    

      

      Copy
    

    
Run it in a terminal, then type /mcp in Claude Code → coding-sessions → Authenticate.

  


  

    
    

      

      Copy
    

    
Run it in a terminal; Codex opens the sign-in page itself.

  


  
No browser on that machine? Generate a token under CLI & MCP access instead.

  





  

  
CLI & MCP access

  
Tokens for the cs command-line client. Each one has full control of your sessions — treat it like a password.

  
On your laptop, cs server add <name> https://this-server signs in through this browser, no copying needed.

  

  

    
    
    
    
    

      

      Copy
    

    
    

      

      Copy
    

    
Codex reads the token from CS_TOKEN; keep its value in a secret store (Next Term Secrets, Keychain), not in a shell file. Claude Code saves this header in ~/.claude.json as plain text.

  

  

    
    
  

  
Connected apps

  
Apps signed in to the MCP connector at /mcp — Claude, Claude Code, Codex. A token above also works there as a fixed Authorization: Bearer header.

  

  





  

  
External MCP connectors

  
Connect MCP servers and choose which tools your agents can use. Access stays off until you grant it.

  

  

    
Add MCP connector

    
    
    
    
    
    
    
Stored encrypted on this server and never shown again.

    
Supports HTTPS MCP servers using Streamable HTTP. Add a token only if the server needs one. For OAuth, leave it empty and sign in from the connector’s settings after adding it.

    
  

  





  

  
Connector

  

    
    
  

  

  

    
Server reports

    
Authentication

    
Tool prefix

    
Last check

    
Tools

  

  

  
Authentication

  
  
  
Changing this removes the saved token or sign-in and every tool approval for this server.

  

  

    
    
    
    
  


  

    

      
Account

      
Signed in

      
Provider

      
Client

    

    

    
    
You approve access on the provider’s page, then come back here.

    
    

      Registered client (advanced)
      
Sign-in works with providers that identify themselves in sign-in responses (RFC 9207) and support S256 PKCE. For others, use a bearer token.

      
A registered client is only needed when the provider cannot register this app itself. Register this redirect URI with it: 

      
Providers that accept client metadata documents fetch ; it must be publicly reachable without a login or challenge.

      

        
        
        
        
        
        
        

        
        
      

    

  


  
Tools agents may use

  
Nothing is granted until you tick it, including tools the server adds later. Granted tools may read or change things on that server. The labels below are the server’s own claims and are not verified.

  


  
New sessions get access

  


  
Running sessions

  

  
Agents that support MCP tool updates see changes within about 10 seconds; others after you resume the session. Calls are checked against these settings every time.


  
Recent calls

  


  

    
    
    
    
    
Changing the URL removes the token and every tool grant, because it may be a different server or account. The tool prefix never changes.

    
  


  
  
  
Removing deletes the token and every grant here immediately. To stop the token working everywhere, also revoke it with the service that issued it.