Who it is forA contributor or a coding agent asked to fix a bug or add a small feature in agent-env.
The problemChanges must follow the repo map, test tiers and pull request rules, and larger changes need an issue first.
The outcomeA working development clone with dependencies installed, and a plan that follows CONTRIBUTING.md and AGENTS.md.
What you need first
- Python 3.11.4 or newer
- uv (https://docs.astral.sh/uv/) or pip
- A running Docker daemon for running environments locally
Steps
- Run
git clone https://github.com/scaleapi/agentenv-framework && cd agentenv-framework. - Run
uv sync --extra dev. - Run
source .venv/bin/activate. - Read AGENTS.md and CONTRIBUTING.md, and open an issue first if the change is larger than a bug fix.
Prompt for your agent
Clone https://github.com/scaleapi/agentenv-framework, run `uv sync --extra dev`, then read AGENTS.md and CONTRIBUTING.md. Report the test tiers and pull request title format you found, and the change you plan for <target bug or feature>. Verify that the virtual environment activates before you edit any code.
Caveat. Pull requests need an approving review from a code owner and green CI, and a change that breaks plugin classes or entry points fails CI unless its title is marked with `!`.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page