@Computer, do it.

    One agent in Slack for your whole engineering team

    Fix the flaky test. Ship the triage agent. Tell me what broke overnight. It writes the PRs, deploys your serverless agents and keeps watch across every repo and ticket.

    ›

    @Computer fix the flaky aut

    #eng ↵
    Thread# eng
    1. M

      Maya10:02

      @Computer, do it: the auth test is flaky again. Find out why and open a PR.
    2. oc

      ComputerAPP10:02

      ✓ Read auth.spec.ts

      ● Bash npm test -- auth · running 12s

      The token is minted before the mocked clock is installed, so it expires mid-test.

    3. steering mid-task

      M

      Maya10:03

      also check the refresh path while you're there
    4. oc

      ComputerAPP10:06

      ✓ Edit src/auth/refresh.ts

      ✓ Bash npm test · 48 passed

      Fixed both. Opened #412.

    5. M

      Maya10:09

      ship the bug triage agent to prod
    6. oc

      ComputerAPP10:10

      ✓ opencomputer deploy triage · v14 live

      It picks up new Linear tickets labelled bug from now on.

    7. next morning

      M

      Maya09:15

      what happened overnight?
    8. oc

      ComputerAPP09:15

      Triage ran 23 sessions: 19 tickets labelled, 3 PRs opened, 1 needs you (LIN-482).

    Illustrative thread · every step streams into Slack as it happens

    Where it fits

    One agent you talk to. Everything else behind it.

    @Computer runs your serverless agents and works across your repos and tickets. Click any box to open its docs.

    serverless agentssession 1session 2session 3agent1databasememoryproject1session 1session 2agent2project2session 1session 2session 3session 4agent3project3repo1repo2linear tickets@Computer
    @ComputerThe agent you talk to in Slack. It writes PRs and provisions, deploys and watches everything above it.Docs ↗

    Every box opens its docs. Scroll sideways to see it all.

    What it does

    A teammate that never logs off.

    With its own computer for every task, and the context of everything your team has built.

    • 01Availability

      Always available.

      Mention it in any channel or DM. Every thread gets its own computer, started from your latest main.

    • 02Context

      Glue for all your work.

      Repos, Linear tickets, docs and your serverless agents, in one conversation.

    • 03Delivery

      Creates PRs for you.

      Work leaves through git: a branch, a push and a pull request for you to review.

    • 04Operations

      Runs your agents.

      “Make an agent that triages new bugs.” It writes it, deploys it and keeps it running.

    • 05Visibility

      Knows what's going on.

      Which sessions ran, what failed, what it cost. Across every project.

    • 06Control

      Steer it mid-task.

      Type while it works and it adjusts. Interrupt, redirect, or let it run overnight.

    Say it in Slack

    Ask in plain words. Get work back.

    Four of the things people ask it every day.

    • @Computer fix the flaky auth test

      ✓ reproduced · 3/10 runs fail

      ✓ patched src/auth/refresh.ts

      ✓ opened PR #412

      Fix

      It reproduces the bug, fixes it and opens a pull request.

    • @Computer make an agent that labels new bugs

      ✓ wrote agents/triage.ts

      ✓ opencomputer deploy

      ✓ triage v1 live

      Build

      Describe an agent; it writes the code and deploys it.

    • @Computer deploy triage

      v13 → v14

      ✓ tests passed

      ✓ v14 live · v13 kept

      Ship

      New versions go out on request; old ones are kept.

    • @Computer what happened overnight?

      23 sessions · 19 labelled

      3 PRs opened

      1 needs you · LIN-482

      Report

      Ask what happened, across every project and agent.

    Underneath

    Everything it runs is a serverless agent.

    Have @Computer write them, or write your own and deploy with one command.

    triage.ts
    import { useModel, useTool } from "@opencomputer/agent";
    
    export default function Agent() {
      useModel("anthropic/claude-sonnet-4.6");
      useTool(labelLinearTicket);
      return "Triage new bug tickets. Label, dedupe, link the PR.";
    }
    Build your own agent →
    Machine
    one per session · shell · filesystem · network
    Lifecycle
    hibernates when idle · resumes in place
    Sessions
    durable · steerable mid-run
    Secrets
    injected outside the machine
    Deploy
    opencomputer deploy · every version kept
    Triggers & toolsSlackGitHubLinearWebhooksSchedulesMCPAny model
    • MinionsStripe
    • InspectRamp
    • HonkSpotify
    • RiverShopify

    Built in house

    Stripe, Ramp and Spotify built their own software factories. Yours comes with someone to run it.

    Get started

    Two ways in.

    Same platform underneath.

    01Recommended

    Let @Computer do it

    1. 01Sign in with Slack
    2. 02Install it in your workspace
    3. 03Mention @Computer with the first task

    02For builders

    Build it yourself

    1. 01npm i -g @opencomputer/cli
    2. 02opencomputer login
    3. 03opencomputer deploy

    Questions

    The short answers.

    Longer ones live in the docs.

    Does it push straight to main?+

    No. Every change leaves as a branch and a pull request for a person to review.

    What can it reach?+

    The Slack channels it's in, and the repos, Linear workspace and serverless agents you connect.

    Can several people use it at once?+

    Yes. Each thread gets its own computer and workspace, so parallel tasks don't step on each other.

    Can I build agents without it?+

    Yes. Serverless agents are TypeScript functions you deploy with the CLI; @Computer is one way to write and run them.

    More in the docs →

    Hand it the first task.

    Add it to Slack, mention it, and see what comes back.