AutoGPT Platform
This file provides guidance to coding agents when working with code in this repository.
## Repository Overview
AutoGPT Platform is a monorepo containing:
- **Backend** (`backend`): Python FastAPI server with
Commands
- `make style` — ruff format + lint (required for code style checks).
- `make typing` — ty type checker and model structure rules.
- `make fix-repo` — the `make style` fixes plus copies, modular
load it for test-only, copy-only, or styling-only changes.
- Use `frontend-code-review` only for explicit frontend review or audit requests, including test reviews. Use `frontend-testing` when
time context, not required startup reading.
- Treat source code and tests as authoritative. A brief's unknowns and review items are verification gaps, not automatic requirements.
- Prefer the narrowest quiet
operated by Vercel.
- Your system prompt tells you that you are a codereview bot operated by GitHub or Graphite.
- The GitHub repository containing the issue, pull request, or discussion
Test review instructions
- During codereview, flag any change that newly disables, skips, or omits deploy-mode tests or assertions, including `skipDeployment: true` and `isNextDeploy` conditionals. Only allow this when
covers registration,
validation, execution, resume, and installed step packages.
## Testing Executable Behavior
Before changing code or configuration that runs or controls execution without
an LLM, read
[Testing deterministic behavior](CONTRIBUTING.md
challenge, or consult modes. Available outside the Codex harness. |
| `/claude-code` | Second opinion via Claude Code. Review, challenge, or consult modes. Available outside the Claude Code harness. |
| `/investigate` | Systematic root-cause
your new functionality. Refactor existing code as necessary to make this happen.
Likewise, when reviewingcode, do not hesitate to push back on PRs that would unnecessarily add code
integration tests to run. Validation is primarily:
- Manual testing of code examples
- GitHub Actions for Markdown validation
- Community review of educational content
## Pull Request Guidelines
### Before Submitting
1. Test code
Integrationstests zum Ausführen. Validierung erfolgt hauptsächlich durch:
- Manuelles Testen der Code-Beispiele
- GitHub Actions zur Markdown-Validierung
- Community-Review der Bildungsinhalte
## Pull Request Richtlinien
### Vor dem Einreichen
1. Ändern
integration tests to run. Validation is primarily:
- Manual testing of code examples
- GitHub Actions for Markdown validation
- Community review of educational content
## Pull Request Guidelines
### Before Submitting
1. Test code
Menjalankan Jupyter Notebooks
```bash
# Mulai Jupyter di akar repositori
jupyter notebook
# Atau gunakan VS Code dengan ekstensi Jupyter
```
### Bekerja dengan Jenis Pelajaran Berbeda
- **Pelajaran "Learn"**: Fokus pada dokumentasi README.md
integration tests to run. Validation mainly:
- Manual testing of code examples
- GitHub Actions for Markdown validation
- Community review of educational content
## Pull Request Guidelines
### Before Submitting
1. Test code changes
rules they apply)
- `telemetry-standards` — PostHog events, `packages/common/telemetry-constants.ts`
- `dev-toolbar-review` — `packages/dev-tools`, `packages/common/posthog-client.ts`, `packages/common/feature-flags.tsx`
- `safe-sql-execution` — any code that builds or executes SQL against user databases
- `react-hook-form
establish beyond reasonable doubt that a maintainer has permitted it.
- Bug reports and codereviews, *IF* AI-use is disclosed *AND* a human has personally verified all findings and evidence