Support Cloud Run services as an execution environment for agents
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
services/hackbot-api/app/jobs.py is hard-wired to Cloud Run Jobs (google.cloud.run_v2.JobsClient/ExecutionsClient, with a hardcoded "agent" container name), and there is no execution-backend abstraction. Introduce one, then add a Cloud Run Services backend for agents that need to stay resident or respond quickly rather than run to completion.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading services/hackbot-api/app/jobs.py, including its use of google.cloud.run_v2.JobsClient, ExecutionsClient, and the hardcoded "agent" container name. Trace how agents are currently launched and where the execution backend boundary belongs. Done means the existing Cloud Run Jobs path is behind an abstraction and agents can also use a Cloud Run Services backend for resident or fast-response workloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100