Skip to main content

​
Core development tools

  • Oso Cloud CLI: validate, test, and deploy Polar policies from the command line.
  • Editor extensions: syntax highlighting, error detection, and in-editor testing.
  • Local testing: use the Oso Dev Server for fast iteration without network calls.

​
Install the Oso Cloud CLI

​
Key CLI commands

Once installed, use these commands in your development workflow:

​
Editor integrations

​
VS Code

Install the official VS Code extension to enable:
  • Syntax highlighting for .polar files
  • Real-time error detection
  • Inline test runner
  • Auto-complete for built-in Polar functions
To install:
  1. Open VS Code Extensions panel (Ctrl+Shift+X)
  2. Search for “Oso”
  3. Install the official extension
Alternative: Download from the VS Code Marketplace

​
Other editors

Oso supports the Language Server Protocol (LSP) for syntax validation, auto-completion, and testing. Use any LSP-compatible editor with the CLI as the language server.
Start the LSP server using the CLI:
oso-cloud lsp
Configure your editor to use this LSP for .polar files.
Install syntax highlighting:
  1. Clone oso-vscode-extension
  2. In JetBrains settings: Editor → TextMate bundles → Add bundle
  3. Select the cloned oso-vscode-extension folder
Install LSP:
  1. Install the LSP4IJ plugin
  2. Go to Language & Frameworks → Language Servers
  3. Add new server:
    • Command: oso-cloud lsp
    • File patterns: *.polar
    • Language ID: polar
Use the built-in policy editor at ui.osohq.com. No setup required. Supports LSP features out of the box.

​
Troubleshooting

CLI not found:
  • Check if the binary is in your system PATH
  • Restart your terminal
  • Verify installation by running: oso-cloud --version
Permission denied:
  • Make the binary executable: chmod +x oso-cloud
  • Use sudo for system-wide installation
VS Code extension not working:
  • Restart VS Code
  • Check the Extensions panel for errors
  • Verify .polar files have syntax highlighting
LSP not connecting:
  • Ensure CLI is installed and on PATH
  • Check LSP configuration in your editor
  • Restart the editor

​
Next steps

Your development tools are ready. Here’s how to start building:
  1. Set up local testing with the Oso Dev Server
  2. Write your first policy in Polar
  3. Model your authorization data as facts
  4. Implement authorization checks in your application