The hourly-ci-cleaner workflow cannot execute because development tools (Go, make, Node.js) are not available in the agent execution environment.
Agentic workflows run in two separate jobs:
- Activation job - Installs tools via setup steps
- Agent job - Runs in separate container without access to installed tools
The agent job only has access to tools specified in the tools: configuration (currently bash and edit), not tools installed in the activation job.
- Workflow run #281 (and all subsequent runs) fail to perform CI cleanup
- Cannot execute:
make fmt,make lint,make test-unit,make recompile - Manual intervention required for all CI failures on main branch
Agent environment check shows tools not available:
$ which make && which go && which node && which npm
(all return: command not found)
$ id
uid=1001(awfuser) gid=1001(awfuser) groups=1001(awfuser),118(docker)
(no sudo access to install packages)Convert from agentic workflow to regular GitHub Actions workflow, as CI cleanup is a deterministic process that doesn't require AI decision-making.
- ✅ Direct access to setup actions (setup-go, setup-node)
- ✅ Simpler execution model
- ✅ Easier to debug and maintain
- ✅ Consistent with other CI workflows
- ❌ Less flexibility in decision-making (not needed for CI cleanup)
- Fix tool access in agentic workflows - Investigate if tools from activation job can persist to agent job
- Use runtime configuration - Check if
runtime:field can specify required tools - Hybrid approach - Use GitHub Actions for commands, agentic for PR creation
- Discovered: 2025-12-22, Run #281
- Impact: High - Automated CI cleanup non-functional
- Priority: High - Requires immediate fix
Until fixed, manually run CI cleanup when main branch CI fails:
make fmt && make lint && make test-unit && make recompileThen create PR with fixes.
.github/workflows/hourly-ci-cleaner.md- Workflow definition.github/workflows/hourly-ci-cleaner.lock.yml- Compiled workflow.github/agents/ci-cleaner.agent.md- Agent instructions