autofeat docs
Use autofeat

Portal

Manage autofeat for your GitHub account or organization.

Sign in with GitHub at portal.autofeat.app. Choose an account or organization in the sidebar. Your GitHub access controls what you can see and change.

Connections

Check the selected account's GitHub connection. Connect a Slack workspace or verify your Slack identity to give instructions in supported Slack threads. Installing the GitHub App grants repository access; it does not by itself enable automatic reviews.

Settings

Set when reviews start, which pull requests to include, and whether new changes request another review. Choose models and providers, instructions, safety controls, and spending limits. Save changes and reload to confirm the saved values.

Model providers appear in priority order. Search by name, model, or provider type, and expand a row to edit it or change its priority. Use Show all to see the full list. Search does not change which providers the agent can use.

Account settings provide defaults for repositories owned by that account. Repository settings can override those defaults. A trusted settings file on the default branch can take priority. The portal shows the effective value and the source where available.

Reviews, fixes, implementation, approval, and merging have separate controls. Turning on reviews does not enable the other actions. Access, policy, pause, and budget restrictions still apply.

Knowledge Base

Add notes, documents, skills, memories, or connected sources. Link entries to repositories and save the Knowledge Base. Review context can use all entries, no entries, or a selected set of entries. Repository links do not choose the entries used for a review. Only connect sources that you trust and are allowed to share with the agent.

For a remote MCP source, enter its public HTTPS address and save it. If the source needs OAuth, use Sign in to connector and approve access with that service. Then sync its resources. The Knowledge Base reads resource text; it does not run the source's tools. You can disconnect its sign-in from the same editor.

The selected GitHub account is the base for knowledge. Verified account conversations can use it without a pull request. Ask the agent to remember a preference, create a reusable skill, or dream about useful lessons from the current conversation. New learning entries are drafts. An account admin can edit, approve, disable, or delete them in the Knowledge Base, then save. Approved entries can inform later conversations. Dream runs only when requested. Dry run allows reflection but does not save new learning drafts. Turn off dry run in account settings to let the agent propose entries.

Organization access requires the GitHub App's Members read permission and an active organization membership. Organizations within an enterprise use their own account knowledge; knowledge is not shared across organizations.

Automations

Create and manage repeatable work for repositories you can access. Choose a trigger and instructions, check the execution policy, and inspect the run history. A saved automation still needs to meet access and policy checks before it can run.

Repository pages

Open repository settings to check configuration and merge requirements. Check work and available controls on the GitHub pull request. A missing permission or failed check must be resolved before the affected action can run. Use the Quickstart to check a first review.

Connected apps

Open Account to review or disconnect apps such as ChatGPT. App access is limited to the accounts and permissions you approved. See Connect ChatGPT for setup and sensitive browser actions.

On this page