Pine Computer overview

Pine Computer is a cloud computer built for AI agents. Add it to your application to give an agent a real browser, a desktop, a shell and files. Give Pine's agent a goal, and it works the browser and the shell for you. A person can watch the desktop and take control when a task needs one.

A Computer keeps its identity from one task to the next. When you stop it and start it again, it restores its cookies, localStorage, passkeys and learned skills. Open tabs and session files are not restored; Persistence explains what comes back.

What a Computer gives you

A real browser. Chrome on a desktop: the agent opens pages, clicks, types, fills forms, uploads files and collects downloads, across as many tabs as the work needs. Sessions

Pine's agent. Give it a goal in plain language. It works the browser and the shell, asks you when it needs an answer, and reports what it did with the files it produced. Steer it while it works, and cap its tokens and time. Agent

A shell and files. Each session has a bash shell beside its browser, a working directory, the input files you hand in, and the outputs of each turn, tracked so you can download them. Files and shell

Skills it learns. Turn a task the agent finished, or a workflow a person demonstrated, into a skill you review before any agent uses it. Built-in skills fill, edit and merge PDFs; write Word documents, PowerPoint decks and Excel workbooks; and pull transcripts from captions, cut, subtitle and mix video and audio. Projects with media generation enabled can also create images and video. Skills

People in the loop. Show the live desktop in your application as a Web Component, or a React or Vue component. A person can watch, take control to sign in or decide something, and hand control back to the agent. Web SDK

An identity that lasts. Sign-ins, passkeys and learned skills come back each time you start the Computer, saved with encryption keys only your server holds. Persistence

Many sessions, one identity. Run several workflows on one Computer at once. Each session has its own window, shell and files, and all of them share the Computer's sign-ins. Sessions

Passkeys. A site can create a passkey on the Computer once the request is approved, and later sign-ins use it. Passkeys are saved with the Computer's state.

A country of your choice. Choose the country the browser reaches the internet from, or let Pine pick one. Pine turns on more countries on request: the console's Capabilities page lists them.

Credentials on your server. Your backend holds the project key and every Computer's keys and tokens. A browser only ever gets a short-lived desktop token. Tokens and scopes

Coming soon

Python and TypeScript server SDKs. Create and control Computers from a Python or Node.js backend, as you can from Ruby and Go today. SDKs

Pause and resume. Keep a Computer's sessions and everything in them while it sits idle, and carry on where it left off.

Start, stop and recover by id. Start a Computer again from its saved state, stop one from any server, and replace a runtime that failed, with requests that are safe to retry.

Scanned documents in any language. Read the text in scanned PDFs and in images, in other languages as well as English.

Speech. Generate spoken audio from text, in a choice of voices or as a two-person dialogue.

Screen recordings and HTML previews. Record a walkthrough of the desktop, and show interactive HTML the agent builds.

Computers and sessions

Create a session for each task or workflow. Each session has its own browser window, shell and work directory, and every session on a Computer shares its browser identity. A sign-in made in one session works in the others.

Connect your application

• Server SDK: create and start Computers, run agent tasks, manage sessions and files, and authorize desktop access. Your backend holds the project key and each Computer's private keys.
• Web SDK: show the live desktop in your application, as a Web Component or a React or Vue component. It connects with a short-lived desktop token from your backend.

See SDKs for languages and downloads. Getting started walks through a server integration, and Web SDK adds the desktop viewer.

Console, Playground and documentation

Manage your project, its members and its keys in the Console. The Playground lets you try Computers before you build an integration; it runs the same Computers your integration gets. The guides, the API reference and the SDK downloads cover integration. Some pages need beta access.

The SDK packages and code namespaces are named pinesandbox and PineSandbox. Use the names and the endpoint shown in the guides.