new tty. same context.

Your data, always in your hands.

Chat from any browser; compute locally.

Authenticate

Local by default

Runs on your host. Compute never leaves the machine it belongs to.

Agent workflows

Structured plans, subtasks, and full turn history you can replay or revert.

Secure core

TLS by default, passkeys, and role-based access enforced locally on every request.

How authentication flows through authd

  1. Authenticate

    Password, MFA, or passkey at authd.

    You sign in once at the central service.

  2. Entitle

    Checks your access-download entitlements.

    authd verifies you may use llmtty.

  3. Mint token

    Issues a central signed token.

    The token proves who you are to your own install.

  4. Local session

    Your install verifies, then mints its own session.

    Verification happens on your host, not in the cloud.

  5. Enforce

    Role-based access on every request.

    Nothing is trusted after login; each call is checked.

How llmtty works

llmtty.com is the front door

Authd handles identity and hands out installers and signed tokens. It never sees your prompts, files, or model output.

Your host does the work

A single binary on your machine talks to your local LLM runtime, keeps history, and runs tools inside your workspace.

Any browser is the terminal

Open your install from a laptop, tablet, or phone and pick up the same conversation, files, and context.

Where it fits