Skip to main content
This quickstart creates a source-controlled Gmail summarizer, connects your Google account, tests the agent locally, and deploys it to OpenComputer.

​
Prerequisites

  • Node.js 22 or newer
  • An OpenComputer account
  • A Google account you can authorize for Gmail

​
1. Install and log in

Install the agents-focused OpenComputer CLI:
Log in and confirm the account the CLI will use:
opencomputer whoami prints your user, organization, and OpenComputer API.

​
2. Choose a template

List the available agent use cases:
Create a Gmail summarizer from the email-triage template:
Initialization generates an immutable UUID and a readable two-word name. Confirm both before the first deployment:
You should see:
The generated name is what people see in the dashboard. The UUID is the unique identifier used by deployments, sessions, channels, and APIs. Generated names vary and can be edited without changing the agent’s identity.
Keep the id stable after the first deployment. Changing it creates a different agent instead of a new version.

​
3. Customize the agent

Open instructions.md and describe the job and its approval boundaries. For example:
The generated project already includes the Gmail tool and its Google connection declaration.

​
4. Commit the agent

Treat the project like any other codebase:
This commits opencomputer.toml, so future deployments use the same identity. Files containing local runtime state and environment secrets are ignored.

​
5. Connect Gmail

Start the Google authorization flow:
Open the authorization link, select the Google account, and approve the requested access. The CLI waits until the connection becomes active.
Connections belong to your OpenComputer user identity, not to one local directory. Give each account an alias, such as personal or work, to connect more than one Gmail account without sharing either account with another user.

​
6. Test locally

Run one task with the local agent:
The CLI starts OpenCode with the project files and a scoped connection to Gmail. You can edit instructions.md or the tools and run the command again until the behavior is right. For an interactive development session, run:

​
7. Deploy

Publish the current source as the production version:
The result includes the stable agent ID and an immutable deployment ID:
Verify that the agent is registered:
Run the deployed agent:

​
Ship an update

Edit any source file, commit the change, and deploy again:
The agent remains gmail-summarizer; the production alias moves to the new immutable version.

​
Next

Agents overview

Learn the project structure and versioning model.

Architecture

Follow source from local development to managed execution.