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
- ..
- backup.test.ts
- backup.ts
- bump.test.ts
- bump.ts
- computer-shape.ts
- computer.test.ts
- computer.ts
- credentials.test.ts
- credentials.ts
- delegate.test.ts
- delegate.ts
- egress.test.ts
- egress.ts
- gate.test.ts
- guard.ts
- hosted.test.ts
- hosted.ts
- hub.ts
- index.ts
- instructions.test.ts
- instructions.ts
- lifecycle.test.ts
- lifecycle.ts
- mentions.test.ts
- mentions.ts
- model-defaults.test.ts
- model-env.test.ts
- model-env.ts
- repo-instructions.ts
- self-hosted.test.ts
- self-hosted.ts
- workflow-hosts.test.ts