Help & FAQ

Foo Guard analyzes AI agent configuration files such as JSON and YAML agent definitions. For Team GitHub scanning, Foo Guard reads `.agentguard.yml` and the supported agent configuration paths it references at an exact commit SHA.

No. Repository scans analyze supported agent configuration files in memory and persist safe summaries only. Foo Guard does not persist raw repository configuration, evidence values, or arbitrary source code.

No. Foo Guard detects and redacts secrets during analysis. Repository scan persistence stores structural finding metadata and safe summaries, not credential values or raw evidence.

Confirm the GitHub App is installed for your organization, required permissions are granted, repository inventory has been synced, and the repository is accessible to the installation. Use the GitHub setup wizard to reconcile inventory if needed.

Update the GitHub App installation repository selection in GitHub, then reconcile inventory in Foo Guard. Enable the repositories you want Foo Guard to govern from the Team repositories page.

A repository must be accessible through the active GitHub installation and your Team workspace must have an active Team subscription or beta entitlement. Suspended installations or lost repository access block enablement.

Foo Guard requires Metadata (Read), Contents (Read), Checks (Read/Write), and Pull Requests (Read). The GitHub App must also have Redirect on update enabled so repository access changes return to Foo Guard correctly.

Push scans run only for enabled repositories with a valid `.agentguard.yml`, active Team entitlement, and a successful GitHub webhook delivery. Verify the repository is enabled, config is valid, and the push modified a scanned path.

Policy Failed means the scan completed successfully but the repository result did not meet the effective organization or repository policy thresholds. Findings and scores are still available for remediation.

A baseline captures an approved repository scan snapshot for regression comparison. Future scans can be compared against the baseline score and finding rule IDs.

Personal workspaces analyze individual agent configurations and saved analyses. Team workspaces add organization governance, GitHub repository scanning, shared policy, audit history, and pooled Team billing.

Owners and admins can remove eligible members from the Team Members page. Removal revokes Team workspace access but does not delete the member's personal Foo Guard account.

Open the Team Members page and use Leave workspace. The final owner cannot leave until another owner is added or ownership is transferred.

Create an API key in Account settings or Team settings, then send it as `Authorization: Bearer agt_live_...` to the Foo Guard API or configure it for the CLI.

Open Log in, choose Forgot password, and submit your account email. If an account exists, Supabase sends a reset link that returns you to Foo Guard to choose a new password.