* Remove agent-browser skill and lockfile The computerUse subagent now provides a full desktop with Chrome, making the bespoke agent-browser skill obsolete. Co-authored-by: Cursor <cursoragent@cursor.com> * Remove agent-browser install and docs from cloud env Drop the agent-browser CLI/headless-Chrome install, skip flag, and docs from the Cursor Cloud Agent Dockerfile, install hook, and notes. Keep the AWS CLI and the Playwright e2e runtime libraries. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Cursor Cloud Agent Environment
This directory defines the checked-in Cloud Agent environment for this repository. Cursor resolves .cursor/environment.json before personal or team saved environments, so this replaces the snapshot-dependent /onboard flow for agents started from this repo.
The Docker build context is .cursor/ only. The Dockerfile intentionally does not copy the repository; Cursor checks out the requested commit at runtime.
What Is Baked Into The Image
- Ubuntu 24.04.
- Docker CE 28.5.2 with
fuse-overlayfsandiptables-legacy, matching Cursor's Docker-in-Cloud guidance for complex compose setups. - Go 1.25.9 from
server/.go-version. - Node 24.11.1/npm 11 via nvm, matching
.nvmrcandwebapp/package.json. - Browser runtime libraries for the Playwright e2e suite.
- AWS CLI v2 for S3 uploads.
- Common Mattermost build/test tools:
make,jq,xmlsec1,pgloader, Git LFS, GitHub CLI, Python 3, and build essentials.
Runtime Hooks
cloud-agent-install.shruns after Cursor checks out the repo. It refreshes nvm, verifies Cursor's multi-repomattermost/enterprisecheckout, runsserverGo dependency hydration, installs webapp dependencies, and runs Playwrightnpm ci.cloud-agent-start.shmaterializes.cursor/cursor.mdas.cursor/AGENTS.md, fixes current-session Docker socket access, starts Docker, waits untildocker infoanddocker compose versionsucceed, then logs in to Docker Hub when credentials are configured.
The environment declares github.com/mattermost/enterprise in repositoryDependencies so Cursor can provide it as part of the multi-repo workspace. Cursor currently clones the repositories as siblings, such as /agent/repos/mattermost and /agent/repos/enterprise, which matches server/Makefile's default ../../enterprise path. The install hook does not clone, pull, or symlink enterprise.
Useful Skips
Set these environment variables to true to shorten startup for narrow tasks:
CLOUD_AGENT_SKIP_ENTERPRISECLOUD_AGENT_SKIP_GO_DEPSCLOUD_AGENT_SKIP_WEBAPP_DEPSCLOUD_AGENT_SKIP_PLAYWRIGHT_DEPS
Expected Secrets
Configure these in the Cursor Cloud Agents dashboard as environment-scoped secrets for the Mattermost Cloud Agent environment.
- AWS uploads use the standard AWS CLI environment variables:
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY, andAWS_S3_BUCKET_NAME. The image only supplies theawsbinary. - Docker Hub pulls use the same variable names as CI:
DOCKERHUB_USERNAMEandDOCKERHUB_TOKEN. The start hook runsdocker loginafterdockerdis ready. MarkDOCKERHUB_TOKENas redacted in the dashboard. When both are set, agents can pull the full defaultmake start-dockerimage set without hitting anonymous rate limits.