Prilog CLI

prilog brings Prilog into your terminal: connect a repository, ship logs and traces, review drafted fixes, and open pull requests without leaving your shell.

✨ What It Does

• 🔐 Authenticates with Prilog through a browser-based login flow.
• 📁 Links the current Git repository to a Prilog project.
• 📡 Ingests logs, traces, and error files from local files or stdin.
• 🐛 Imports an open issue from a public GitHub upstream for analysis against a connected fork.
• 🧭 Lists detected errors by status, including pending fixes.
• 🛠️ Starts Prilog analysis for an error and opens the dashboard review.
• 🔎 Prints generated diffs directly in the terminal.
• 🚀 Creates pull requests for generated fixes in the connected repository.

📦 Install

Homebrew

brew install prilog-ai/tap/prilog

One-Line Installer

macOS and Linux:

curl -fsSL https://raw.githubusercontent.com/Prilog-ai/prilog-cli/main/install.sh | sh

The installer detects your operating system and CPU architecture, downloads the matching release asset, verifies checksums when available, and installs the prilog binary into /usr/local/bin.

To install somewhere else:

curl -fsSL https://raw.githubusercontent.com/Prilog-ai/prilog-cli/main/install.sh | PRILOG_INSTALL_DIR="$HOME/.local/bin" sh

Verify the install:

prilog version

⚡ Quick Start

Authenticate once:

prilog login

Connect the current repository to a Prilog project:

prilog init

Check the active account, organization, project, and fix totals:

prilog status

Ingest a local log, trace, or error file:

prilog ingest ./logs.log

Or import a public GitHub issue after connecting your fork of that repository:

prilog issue import https://github.com/medusajs/medusa/issues/16487

Review and act on detected errors:

prilog list pending
prilog fix <error-id>
prilog diff <error-id>
prilog pr <error-id>

🧰 Commands

Command	Description
prilog login	Authenticate or switch Prilog accounts.
prilog init	Link the current repository to a Prilog project and launch onboarding.
prilog status	Show the active user, organization, project, log totals, and fix totals.
prilog config	Show local CLI configuration for the current repository.
prilog config path	Print global and repository config file paths.
prilog ingest [file]	Upload logs, traces, or errors from a file or stdin.
prilog issue import <url|owner/repo#number>	Import an open public GitHub issue into the active project. The connected code repository must be your fork of that upstream.
prilog list [filter]	List recent logs and errors. Filters: all, pending, processing, completed, failed.
prilog fix <id>	Queue Prilog analysis for an error.
prilog diff <id>	Print the generated fix diff in the terminal.
prilog pr <id>	Create a pull request for the generated fix and print the PR URL.
prilog version	Print the installed CLI version.

🧪 Example Workflow

# Authenticate and connect this repository
prilog login
prilog init

# Send telemetry from a local file
prilog ingest ./production-errors.log

# Find pending issues and start a fix
prilog list pending
prilog fix 018f4a2e-7c2b-7b9d-ae4a-0ef5d4f9a101

# Review locally or create a PR
prilog diff 018f4a2e-7c2b-7b9d-ae4a-0ef5d4f9a101
prilog pr 018f4a2e-7c2b-7b9d-ae4a-0ef5d4f9a101

Public upstream contribution

Use one Prilog project per upstream repository. Fork the upstream into the GitHub account connected to Prilog, install the Prilog GitHub App on that fork, and select the upstream default branch during service setup. Then:

prilog issue import medusajs/medusa#16487
prilog fix <error-id>
prilog diff <error-id>
prilog pr <error-id>

The importer rejects closed issues, pull request URLs, unrelated forks, and forks configured on the wrong base branch. prilog pr pushes the generated branch to the connected fork and opens a cross-fork pull request against the issue's upstream repository with the connected GitHub user as the PR author.

🔐 Security

Authentication uses a browser-based Prilog flow. Access and refresh tokens are stored in your operating system's user config directory, while repository project metadata is stored in .prilog/config.json.

Every command that reads or mutates Prilog data is authenticated against the Prilog API and authorized against the active organization and project.

Recommended hygiene:

• Do not commit .prilog/config.json if your repository policy treats project metadata as private.
• Run prilog login again to switch accounts or refresh local credentials.
• Use prilog config path to find and remove local config files when testing a clean setup.

🧑‍💻 Development

Requirements:

• Go 1.23 or newer
• Git

Common tasks:

go test ./...
go vet ./...
go build -o prilog .

The CLI is intentionally stdlib-only. The source is split around user-facing commands, auth, HTTP transport, repository metadata, config persistence, and output formatting so the command surface stays easy to audit.

🤝 Support

• Product and CLI issues: Prilog-ai/prilog-cli issues
• Homebrew packaging issues: Prilog-ai/homebrew-tap issues
• Website: prilog.ai