Claudeagent and ClaudeagentA public repository's job is no longer handed to a self-hosted runner in host mode, only to fail there. Runners say how they are isolated on every poll as well as when they register (an older g1t ignores it), so a runner restarted with or without Docker is known as it is now; the queue gives a host-mode runner no public repository's jobs or agent work, reading each repository's visibility once a poll, and a job that no online runner which may take it could, sandboxed and with its labels, group and repository, waits saying "Waiting for a sandboxed runner: this repository is public, and host-mode runners don't run public repositories' jobs." until one comes online. A runner that never said how it is isolated is given the job as before and refuses it itself. The Self-hosted runners guide says so, with the message in its troubleshooting table.dc35a8aHistory
- ..
- about.rs
- addresses.rs
- alerts.rs
- audit.rs
- billing.rs
- blobs.rs
- checks.rs
- customize.rs
- deploy_keys.rs
- deployments.rs
- folios.rs
- lib.rs
- limits.rs
- logs.rs
- mcp.rs
- mirrors.rs
- notifications.rs
- oauth.rs
- oidc.rs
- openapi.rs
- operations.rs
- packages.rs
- people.rs
- pins.rs
- projects.rs
- protection.rs
- reference.json
- renamed.rs
- responses.rs
- rest.rs
- rules.rs
- run_artifacts.rs
- runners.rs
- security.rs
- token_policy.rs
- toolkit.rs
- tools.rs