Quickstart

Prerequisites

You need a Prilog account and a GitHub repository you can authorize. Sign in at app.prilog.ai. For this terminal workflow, also install Git and the Prilog CLI.

1. Install and sign in

Install with Homebrew on a supported Homebrew environment:

$
$
$brew install prilog-ai/tap/prilog
prilog version
prilog login

For macOS or Linux without Homebrew, use the CLI install instructions.

prilog login opens a browser. Complete sign-in with the Prilog account that owns your workspace.

2. Choose a project and connect code

Run these commands inside your application's Git repository:

$
$
$prilog projects
prilog create-project "Payments"
prilog add-repo

If you already have a project, run prilog use-project "Payments" instead of creating one. add-repo opens the GitHub authorization and Add service flow in Prilog. Select your repository and branch and finish setup in the browser using the same Prilog account as the CLI.

$prilog status

Confirm the organization and project before sending logs. Run add-repo again to add another service to the selected project.

3. Send a real error

Upload a file containing an error from the connected application:

$
$prilog ingest ./production-errors.log
prilog list pending

You can also pipe selected log content into prilog ingest. Include the error message, stack trace, and relevant context. Remove credentials and sensitive free-form data before uploading.

For continuous collection, use Prilog monitoring or connect your existing observability provider in the dashboard.

4. Generate and review a fix

Copy an error ID from prilog list. Replace ERROR_ID below with that ID:

$
$
$prilog fix ERROR_ID
prilog list processing
prilog diff ERROR_ID

Analysis runs asynchronously. Check its state in the dashboard or CLI; the first diff request may arrive before a code change is ready. See fix states if no diff appears.

5. Open a pull request

After reviewing the generated change:

$prilog pr ERROR_ID

The command returns the pull request URL. Review CI and merge through your usual GitHub workflow. Project automation settings can also control how fixes are handled.

Next steps

Use the CLI reference for automation and public issue imports, plugins for coding agents, or MCP for a hosted assistant connection.