Skip to main content

​
Configuration

​
paragon.json

Create a paragon.json file in your project root to configure Paragon behavior: 
{
  "automations": [
    {
      "name": "Build & Test",
      "prompts": [
        "Run the build",
        "Run all tests",
        "Report any failures"
      ]
    }
  ]
}

​
PARAGON.md

Use /init to generate a PARAGON.md file that provides project context to Paragon. This file should contain:
  • Project structure overview
  • Key technologies and frameworks
  • Development conventions
  • Important architectural decisions

​
Authentication

​
Login

paragon auth login
Opens a browser-based authentication flow to connect your Paragon account.

​
Status

paragon auth status
Displays current authentication state and account information.

​
Logout

paragon auth logout
Removes stored credentials.

​
FAQ

Use the /model command to open the model picker and select a different model. Your conversation context is preserved.
Sessions are separate conversations with independent context. /compact summarizes your current session and starts fresh with that summary as context.
MCP (Model Context Protocol) servers extend Paragon’s capabilities by connecting to external tools and services. Configure them via /mcp to give Paragon access to filesystems, databases, APIs, and more.
Yolo mode (/approvals) auto-approves all tool executions. Use it only when you trust the operations being performed and want faster iteration. You can toggle it off at any time.
Monitors are scheduled tasks that run Paragon prompts at regular intervals. They require Polarity authentication and run in the background based on your configured cadence.
Paragon requires an internet connection to communicate with AI models. Some MCP servers may work offline if they only access local resources.

​
Getting Help

  • Use /help to view keyboard shortcuts
  • Run paragon --help for CLI options
  • Contact [email protected] for assistance