efficiently with the AutoGPT repository.
## Repository Overview
**AutoGPT** is a powerful platform for creating, deploying, and managing continuous AI agents that automate complex workflows. This is a large monorepo (~150MB
commands
- Pages are **ICommand** implementations — they can be used anywhere commands are used
- Always **Deploy** (not just Build) to register the MSIX package
- After deploying, use the **Reload** command
Updates with Code Changes
- PRs with code changes shouldn't update `/documentation` - docs deploy on merge, code on release. Use `unlisted: true` or remove/hide docs.
## Project-Specific Context
- This
uses:
- MSBuild
- vcpkg for C++ dependencies
- NuGet for C++ and .NET dependencies
### Running/Debugging
1. Deploy solution: Build > Deploy Solution
2. Run from command line: `wingetdev`
3. For debugging:
- Right-click
production
- Database migrations are automatically applied on startup
- HTTPS is required for production deployments
## UI Pull Request Review Guidelines
**IMPORTANT: When reviewing UI pull requests, you MUST follow the comprehensive
importer/generateFont.js` (Regular/Filled/Light/Resizable) feeding React font condition and Flutter/iOS/Android.
- Native (Android/iOS/Flutter): Produced by `importer` deployment scripts (`deploy:android`, `deploy:ios`, `deploy:flutter`) which transform assets into vector drawables / PDF assets / Dart
fast-track.
- **Verify claims**: If the PR cites benchmarks, adoption numbers, or production deployments, spot-check them. Unverifiable claims are a red flag.
- **Scope proportionality**: A small or unknown project
dependencies beyond `Az.Accounts`. All helper functions are
defined inline. This is intentional — it keeps deployment simple (copy one file).
### Execution flow
1. **Authenticate** — Validates `Az.Accounts` context, refreshes ARM bearer token
prove semantic markers/stable content with no raw fence; local validation alone is not remote deployment proof.
The 4 `serves` values that every module is mapped to: `attention` | `readability` | `memorability` | `conversion
Team Foundation Server. These instructions will help you understand how to build, test, and deploy tasks effectively.
## Repository Overview
This repo provides open examples of how Azure Pipelines tasks
force` or skip hooks with `--no-verify`
4. After merge, optionally deploy: `./scripts/deploy-acr.sh`
### CI/CD Pipeline
Pull requests automatically run the CI workflow (`.github/workflows/ci.yml`):
1. **Format Check**: `cargo
node**: Lowercase. A worker machine in Kubernetes (physical or virtual).
**pod**: Lowercase. The smallest deployable unit in Kubernetes, containing one or more containers.
**container**: Lowercase. A lightweight, standalone executable package
with three main components:
- **Edge Agent** (`edge-agent/`) — C# service that manages module lifecycle, deployments, and desired-state reconciliation via IoT Hub twin
- **Edge Hub** (`edge-hub/`) — C# service acting