Skip to content
The Docs Report
Tuesday, September 29, 2026NewsletterRSS

Jamdesk Puts JWT Sign-In on Every Plan and Builds From Bitbucket

Jamdesk's Sept. 23 update adds JWT login on every plan, Bitbucket Cloud builds and one llms-full.txt per language for multilingual docs.

3 min read

Jamdeskllms.txt

Isometric 3D illustration of glossy cobalt blue old-fashioned keys on a tiled floor

Jamdesk now lets teams gate a docs site behind their own login system with JWT authentication, included on every plan, and can build sites from Bitbucket Cloud as well as GitHub, according to the company’s Sept. 23 changelog. The same release splits llms-full.txt by language for multilingual sites.

Sign-in without a shared password

Private docs no longer need a shared password: Jamdesk now checks a token signed by the customer’s own backend. A team turns on auth.jwt in docs.json, generates an Ed25519 signing key in settings and has its backend sign a short-lived token when a user opens the docs. Jamdesk verifies the token and starts a per-user session that lasts up to 30 days.

Pages can be limited to groups. Adding groups: ["admin"] to a page hides it from anyone whose token lacks that group, and they get a 404. Public paths and pages marked public: true stay open, so a changelog or status page can sit outside the login. The token can also pre-fill the API playground with the visitor’s own credentials. Jamdesk says the feature is included on every plan, and teams can move over from password protection without a gap in coverage.

Bitbucket, with limits

Bitbucket Cloud repositories can now build and deploy Jamdesk sites, but the web editor, Fix with AI and AI translation stay GitHub-only for now. Because Bitbucket doesn’t retry a failed webhook, Jamdesk also checks the branch every five minutes so a lost delivery still triggers a build.

One llms-full.txt per language

Multilingual sites now publish a full-content file per language, such as /fr/llms-full.txt, so an agent can load one language instead of all of them. The root /llms-full.txt still contains every language, so existing tools see no change, and single-language sites are unaffected. The docs root also answers Accept: text/markdown requests with the first page in the navigation. Jamdesk said sites without an index.mdx used to return a 404 there, “which broke the first request most agents make.”

The release also adds an opt-in autoRedirect setting that sends first-time visitors to their browser’s language, a frontmatter field to override a page’s “last updated” date, and a nocopy option that removes the copy button from a code block.

Key takeaways

  • JWT authentication with Ed25519 keys and per-user sessions of up to 30 days is included on every Jamdesk plan.
  • Bitbucket Cloud builds work, but the web editor, Fix with AI and AI translation remain GitHub-only.
  • Multilingual sites get one llms-full.txt per language; the root file still has everything.
  • The docs root now returns Markdown to agents instead of a 404.

The take

We’d have expected JWT sign-in to sit on a paid tier, since gating docs behind a company’s own login is the kind of feature that justifies one. Jamdesk includes it on every plan. We’d call the Bitbucket support partial: a team that edits in the browser or leans on AI translation is still tied to GitHub. The per-language llms-full.txt and the Markdown root fix are small, but we like where they aim. They go after the first request an agent makes, which Jamdesk admits its own sites were failing until this release.

Twelve Top Companies Use llms.txt to Tell AI What to Recommend

llms.txt