Salience

Your tools leave you to connect the dots in your head. Salience connects them for you.

Your IDE knows where you are in the code. Salience knows where you are in the work — and so can your AI agents.

Salience is a macOS and Linux app that watches your branches, tickets, pull requests, builds, observability and local environment, and works out how they fit together: the ticket behind a branch, the PR it became, the image that PR built and where that image is running. That's how it catches what no single tool can see: a merged PR whose ticket is still open, branches and worktrees you no longer need, the commits that went out in the last deploy.

It holds what your tools don't. Drop a spec, screenshot or log onto a ticket, PR or project; pin a note to anything; attach the Slack message where the decision was made. They join the same picture.

Create your own dashboards, keep it on a second screen for a quiet overview, dig into the details when you need them, or give your agent the same joined-up context.

Salience is in alpha. Expect rough edges.

Downloads · Releases · All documentation

Start here

• Get started — install Salience, add a project and connect your first tool.
• Concepts and terminology — understand entities, correlations, units of work, situations, tiles and pages through a worked example.
• Connect your tools

One piece of work, across several tools

The Docker setup ticket, its branch, pull request and build checks, brought together in Salience.

Follow the example

Branch -> Pull request -> CI -> Checks on self hosted runners -> the infrastructure they run on

· More screenshots

Connectors

Connector	What it brings in
Git	Local branches and worktrees, read straight from disk
GitHub	Pull requests, reviews, conversation and GitHub Issues
CI	Check results for your pull requests and branches, from GitHub Actions and any CI that reports to GitHub
Jira	Tickets from the boards you pick
Sentry	Unresolved issues, with stack traces mapped onto your code
Slack	Messages that mention you, ready to attach to a ticket, PR or project
AWS	ECR images, ECS clusters, task definitions and running tasks
Docker	Compose services and their containers, with start, stop and restart

Every connector is read-only, except the Docker controls, which start and stop your local containers when you ask. GitLab and Linear are coming soon.

Build your own dashboards

Pick from over 45 tiles to build a page around the work you're doing: units of work, branches and worktrees, reviews and tickets, builds and containers, agents and app health.

Explore further

• Integrations
• Using Salience — workflow guides, including outlines being developed.
• MCP server
• Code Graph
• Privacy and security — understand where your data lives and how to inspect connections.
• About Salience

Roadmap

• Gitlab Connector
• Proxmox Connector
• Linear Connector
• Dedicated agent page with quick actions to resolve situations, a way to share curated context with an agent and more.
• Graph Explorer
• Javascript support for the code graph

If you have any suggestions or things you'd like to see in Salience open an issue or join the Discord.

Help and feedback

For a problem with the app, open an issue with your platform, app version and steps to reproduce it. Remove credentials and private project information from logs and screenshots.

For questions and discussion, join the Discord.

This repository

This repository contains Salience's documentation website and release distribution.

Documentation changes can be submitted as pull requests here.

Building the docs

Use Node.js 20 or newer, run npm ci, then npm run docs:dev for a local preview or npm run docs:build for a production build. Run npm test to check release selection and download metadata handling.

The download page fetches GitHub release metadata at build time using docs/releases.data.js. It selects the most recently published non-draft release, including prereleases, and displays its supported macOS and Linux installers. Filenames, sizes, links and SHA-256 hashes come from GitHub; missing hashes are explicitly marked as unavailable. Updater archives and signatures are excluded. A failed API request or a release without supported installers fails the build, leaving the previously deployed site in place.

Building requires network access to GitHub. Set GITHUB_TOKEN locally if you need authenticated API rate limits; the Pages workflow supplies its own token. The token is used only by the build and is never included in the site data.

Pages rebuilds on documentation pushes, release publication or edits, and daily to catch late asset uploads and releases created by another workflow's GITHUB_TOKEN. For an immediate refresh after uploading assets, run Deploy docs to Pages from the Actions tab using Run workflow, or dispatch deploy.yml from the release pipeline after all uploads finish. No generated release metadata needs to be committed.