daemon.cjs · part 23

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-agent-host/dist/agent-host-daemon/dist/bin/daemon.cjs, part 23. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

use strict

use strict

use strict

use strict

${skill.fullPath ?? ""}
${skill.description ?? ""}

Set up ${repoName} environment

use strict

Report deployments to Cursor Rollouts

Skip changes that cannot affect what runs in any deployed environment:

- documentation-only changes (Markdown, docs sites, code comments, changelogs)

- formatting, lint, or typo fixes with no behavior change

- test-only changes (test files, fixtures, snapshots)

Monitor everything else, including dependency bumps, configuration, and infrastructure changes.

Set up a new development environment for this codebase. Run the relevant applications and demonstrate that the environment works end to end.

Set up a new development environment for this codebase. Follow the “Set up a new environment” workflow in the env-setup skill. Run the relevant applications and demonstrate that the environment works end to end.

Update the existing dashboard-managed development environment. Preserve working behavior and validate the updated environment end to end.

Update the existing dashboard-managed development environment. Follow the “Update a DB-managed environment” workflow in the env-setup skill. Preserve working behavior and validate the updated environment end to end.

Update the repository-managed development environment. Treat the repository configuration as authoritative.

Update the repository-managed development environment. Follow the “Update a repository-managed environment” workflow in the env-setup skill, and treat the repository configuration as authoritative.

Development environment setup

use strict

${SCM_REF_NOT_FOUND_MESSAGE_PREFIX} "${args.ref}" does not exist in ${args.repository}. It may have been deleted after its pull request merged. Choose an existing branch and try again.

${getScmProviderDisplayName(args.provider)} repository ${args.repository}

${SCM_AUTH_FAILED_MESSAGE_PREFIX} ${target}. ${SCM_AUTH_FAILED_REMEDIATION[args.provider]}

${CLOUD_AGENT_START_PAYLOAD_TOO_LARGE_MESSAGE_PREFIX} ${detail} This is often caused by a long prompt, large conversation history, or (for webhook-triggered automations) including the entire webhook payload in the run's context. Reduce the amount of context included in this run, then try again.

GitHub blocked repository access because the repository owner has an IP allow list enabled.

use strict

Your environment snapshot has expired after inactivity.

Your environment snapshot is invalid.

The environment snapshot you requested does not exist, or you do not have permission to access it.

Failed to start the development environment. The update script in your configuration failed during VM startup.

Failed to start the development environment. A shell startup file in this environment (for example ~/.bashrc) is invalid and exits with an error when a login shell starts. Fix the shell startup file in your environment image or snapshot, then try again.

Failed to start the development environment. The build process failed. Please check your Dockerfile.

Failed to pull the Docker image for this environment. The registry denied access or the image was not found. Check that the image exists and that any required registry credentials are configured.

Repository URL is required for worker connections

Worker Disconnected

Cursor lost connection to the worker during tool execution.

No self-hosted workers were available for this repo.

All matching self-hosted workers for this repo were busy with other runs. Wait for a run to finish or add more workers, then try again.

You can try again by writing a follow-up below.

We are experiencing issues loading your environment snapshot.

GitHub blocked repository access because this organization or repository uses an IP allow list.

${GITHUB_IP_ALLOWLIST_USER_FACING_MESSAGE_PREFIX} Ask a GitHub org admin to allowlist Cursor's egress IPs, then start the agent again. See ${GITHUB_IP_ALLOWLIST_DOCS_URL}

This repository is empty. Add an initial commit to the repository and try again.

The starting branch or commit

The connection to the git remote dropped while downloading the repository. This is usually temporary — try again.

The agent couldn't check out the repository

${SCM_CHECKOUT_FAILED_MESSAGE_PREFIX} from the source-control provider. The provider (for example GitHub) may be down or unreachable, or Cursor's access to the repository may not be working. Check the provider's status and Cursor's repository access, then try again.

Azure DevOps

Ask an admin to reinstall the Cursor GitHub App on the repository's owner and grant it access, then start the agent again.

The stored GitLab token may have been revoked or expired. Reconnect the GitLab integration, then start the agent again.

The stored Bitbucket credential may have been revoked or expired. Reconnect the Bitbucket integration, then start the agent again.

The stored Azure DevOps credential may have been revoked or expired. Reconnect the Azure DevOps integration, then start the agent again.

Cursor could not authenticate with

${SCM_AUTH_FAILED_MESSAGE_PREFIX} the source-control provider for this repository. Its stored access may have been revoked, expired, or lost. Reconnect the integration for this repository, then start the agent again.

This run's request is too large to start.

We encountered an unexpected error repeatedly.

Session expired

Usage limit reached

GitHub IP allow list blocks repository access