Connor Yoh 19785e40a9 Do not treat "have not asked yet" as "not linked"
A linked self-hosted instance is still shown the connect prompt, the sidebar
"Link Stirling account" button and the feature gates.

linkState has three values and none of them is "unknown", so LinkProvider opens
at "unlinked" and a separate status call corrects it. useConnectGate reads
!isLinked, and its loading flag covers only the app-config query, so in the
window between app-config landing and the status arriving a linked instance
looks unlinked: the prompt fires and the gates close.

The version users actually hit is worse, because it never corrects itself.
useAccountLink.refresh swallows a failed status call into { linked: false }. A
401 from a lapsed admin session, a 5xx, a dropped connection, and nothing
retries: the instance then reads as unlinked for the rest of the session.

So the context now carries whether the status has been read back at all.
Anything that blocks waits for it; the gate holds open until then, and stays
open if the call never succeeds. A gate that cannot read its own precondition
should not be the thing standing in the way, and the real enforcement for these
features belongs on the server regardless.

The prop defaults to true so a pinned state in a story or test is still
believed as given. Only the app passes false, because only the app has to ask.

Tests cover the three answers that were being conflated: not yet known, never
knowable, and genuinely unlinked, the last so this cannot quietly decay into
"never gate".
2026-09-02 13:27:45 +01:00
2026-08-13 14:09:25 +00:00
2026-07-11 12:48:53 +01:00
2026-03-25 11:00:40 +00:00
2026-07-17 10:16:06 +00:00
2026-03-25 11:00:40 +00:00

Stirling PDF logo

Stirling PDF - The Open-Source PDF Platform

Stirling PDF is a powerful, open-source PDF editing platform. Run it as a personal desktop app, in the browser, or deploy it on your own servers with a private API. Edit, sign, redact, convert, and automate PDFs without sending documents to external services.

Docker Pulls Discord OpenSSF Scorecard GitHub Repo stars

Stirling PDF - Dashboard

Key Capabilities

  • Everywhere you work - Desktop client, browser UI, and self-hosted server with a private API.
  • 50+ PDF tools - Edit, merge, split, sign, redact, convert, OCR, compress, and more.
  • Automation & workflows - No-code pipelines direct in UI with APIs to process millions of PDFs.
  • Enterprisegrade - SSO, auditing, and flexible onprem deployments.
  • Developer platform - REST APIs available for nearly all tools to integrate into your existing systems.
  • Global UI - Interface available in 40+ languages.

For a full feature list, see the docs: https://docs.stirlingpdf.com

Quick Start

docker run -p 8080:8080 docker.stirlingpdf.com/stirlingtools/stirling-pdf

Then open: http://localhost:8080

For full installation options (including desktop and Kubernetes), see our Documentation Guide.

Resources

Support

Contributing

We welcome contributions! Please see CONTRIBUTING.md for guidelines.

This project uses Task as a unified command runner for all build, dev, and test commands. Run task dev to get started running the editor, run task to see the most common commands, or see the Developer Guide for full details.

For adding translations, see the Translation Guide.

License

Stirling PDF is open-core. See LICENSE for details.

S
Description
#1 Locally hosted web application that allows you to perform various operations on PDF files
Readme MIT
1.3 GiB
Languages
Java 45.9%
TypeScript 44.7%
Python 3.9%
CSS 2.4%
Shell 0.8%
Other 2.2%