Your Claude Code. Your Lab. Connected.

Stop alt-tabbing between terminal and browser. Run Claude Code inside Lab and see every file, every diff, every message in a rich interactive workspace.

Start setup See How It Works

1K4 Lab · my-saas-app

Claude Code Bridge Connected

Claude Codebridge

File Activity

src/auth/session.tsdone

src/auth/middleware.tsdone

src/auth/oauth.tswriting...

Refactor the auth module to support OAuth2 with PKCE flow. Keep backward compat with existing sessions.

Claude Code

I'll start by creating the PKCE helpers in src/auth/pkce.ts, then update the session middleware. Let me read the existing session logic first.

Claude Code

Done with session.ts and middleware.ts. Now updating the OAuth provider to use the PKCE verifier.

Send a message to Claude Code...

src/auth/session.tsAcceptReject

  import { verify } from "jsonwebtoken";
  import { Session } from "./types";
 
- export function createSession(userId: string) {
+ export function createSession(userId: string, pkce?: PKCEChallenge) {
+   const verifier = pkce?.verifier;
    const token = sign({ userId }, SECRET);
    return { token, expiresAt: ... };
  }

Filesmain

▼src

▼auth

session.tsM

middleware.tsM

oauth.tsM

pkce.tsA

▶utils

package.json

Visual workspace

Terminal is powerful but blind. Lab shows your files, documents, slides, and deployments as rich interactive previews.

Persistent sessions

Switch between the 1K4 agent and Claude Code in the same session. Same history, same files, no context lost.

Zero cost

The bridge is free. You use your own Claude Code subscription. Lab just gives you the UI and workspace tools on top.

One command. Done.

Connect Claude Code to Lab in seconds.

$ npx -y -p @1key4ai/mcp-lab@latest mcp-lab setup --setup-token YOUR_SETUP_TOKEN

Placeholder shown. Real setup token issued after sign-in on the install page (P0 security gate).

Start setup