Get started / 5 MIN READ
Run on your computer
Start the bundled UI and runner, sign in to your tools, and keep your workspace on your machine.
Get the Local package
Obtain the release archive for your operating system from your Papliba administrator. Release artifacts are currently distributed through the project’s Azure DevOps pipeline, not a public download service. Archives are unsigned; a signed installer and macOS notarization are not included yet.
The package contains the interface, runner, and .NET runtime. You do not need Node.js or a separate .NET install to run it. Extract it into a new folder; keep your existing application-data directory when upgrading.
Launch the workspace
- On macOS, run Start Papliba.command. On Linux, run the launcher with Bash. On Windows, run Start-Papliba.ps1 under your organization’s PowerShell policy.
- Keep the launcher console open. It starts the backend on 127.0.0.1:5127 and opens /app/ in your browser.
- Close the launcher or press Ctrl+C to stop the backend. Closing a browser tab alone does not stop it.
Connect your tools
For Azure, install Azure CLI and the resource-graph extension on this computer. Sign in before opening an Azure view. GitHub supports a local GitHub CLI session or a personal access token. The launcher does not silently install these dependencies.
az login --tenant <your-tenant-id>
az extension add --name resource-graph
# Optional GitHub connection
gh auth loginData and backups
Workspaces use SQLite in the operating system’s application-data directory. PAPLIBA_DATA_DIRECTORY can select another location. Stop Papliba and back up the complete data directory, including encryption keys and files. Do not share that directory between running installations.
Azure and GitHub requests still contact their respective cloud services. Optional AI assistance can send prompts and script contents to the configured AI provider. Set PAPLIBA_ALLOW_AI=false to disable it. Local is not an offline mode.