AI picker chevron fixed; home polish (no section titles, + Add card
matches card shape, empty slots invisible until hover); performance
toggles — Pithos on-demand with a pithosAtLaunch opt-in, Hermes
auto-restore now a Settings > Performance > Startup toggle.
Horizontal Silent Mode cards with icon+title on the left and
description on the right, semi-transparent card backgrounds, refreshed
tagline and address-bar tip.
Right-click on a tab now shows a Save page as submenu with PDF and
Image (PNG) items. PDF uses webContents.printToPDF (A4, prefers CSS
page size, prints backgrounds); PNG uses webContents.capturePage of
the visible viewport. Both open a save dialog with a filename derived
from the tab title or hostname, write to the chosen path, and register
the result in the downloads list.
The Claude connector's design doc now ships at
theseus.x/dev/claude-connector/DESIGN-claude-connector.md so readers
on the site do not have to leave for the forge; the Developers page
links the local copy first and the forge mirror alongside it.
Hero mark joins the Theseus Navigator wordmark in a readable translucent
pill; left-column slot area widens to roughly five columns of 72 px
tiles so more quick-launch icons fit without crowding.
- Home page now shows the left-column links and the Silent Mode cards
as two self-contained panels; slot icons default to a size closer to
Windows desktop shortcuts.
- Opt-in Claude connector (bundled extension, off by default) gains
three hardenings: origin re-check before every CDP read/input,
bearer-token rotation on stop, point-level password-field refusal in
click(x, y) without a ref.
The connector ships off by default with the next Theseus release; users
need the setup steps (claude mcp add with the panel's token) and a plain
account of what it can and cannot do before turning it on.
The sidebar strip's AI engine picker is now a styled HTML overlay with
real per-engine icons, acid-accent highlight for the current engine,
and a settings shortcut at the bottom — replacing the plain native
menu. One click selects an engine and opens it in the left panel.
- Left-column slot grid grows to fixed 3-col cells with visible drop
targets. Links pin to a specific cell when dropped on an empty slot;
dropping on a filled slot swaps the two. Unpinned links auto-flow.
- Ariadne.X home card switches to the brand kit's ivory-on-dark bust
(variant-ivory-glow) in place of the terracotta pottery sketch,
which was designed for cream backgrounds and got lost on dark.
List 0.3.104 with its hashes so the updater and the download pages offer it. The theseus.x page also gets the right hashes again (they had been left on an older build), and the Theseus page keeps the ariadne-v0.29.apk wording that was already live.
- Sidebar panel context menu (Copy image + Save as + link menu +
back/forward/reload). Fixes a long-standing gap where WhatsApp Web
and other sites that intercept right-click left users with no way
to copy an image from the sidebar panel.
- Hermes mark in the sidebar strip tightens its viewBox so the V-fold
and wings fill the icon instead of sitting in whitespace.
- site/releases: 0.3.90 block above 0.3.89 with the desktop-home write-up
and the shipped SHA-256s (8c7bdea…, 6952b9c…).
- site/theseus + site-theseus-x: bump the download card to 0.3.90 and
update the fallback hashes to match. The theseus-x page continues to
fetch the live manifest; the fallback kept in sync for offline reads.
- site/releases-manifest.json: 0.3.90 entry prepended. The dl copy was
scp'd and dl-latest.sh regenerated the /latest/ redirects on the VPS.
Tabs go back into another window, and the sidebar gets Proton Mail, its
own order and real icons; the download pages and the update manifest
point at it.
The trust note said a community extension runs with the same access as any
add-on. It now runs in its own process with read access to its own folder
only; the note says what that does and does not cover, and the build steps
list what an author has to change (promises, bundled dependencies, no
request filters). To be deployed with the Theseus release that ships the
sandbox, not before.
The Sirius.X / Theseus.X / Ariadne.X / Hephaestus.X links in the family
topnavs and body copy were written as full https URLs — href="https://sirius.x/".
In Theseus's own browser (where the current page is served over the bns://
scheme) that absolute URL triggers the gateway-fallback path on top of the
current host, producing URLs like bns://theseus.x/bns/sirius.x/ that then
accumulate segments as the user clicks around.
Switched 56 cross-family link hrefs to protocol-relative (href="//sirius.x/"
etc.). Protocol-relative URLs inherit the scheme of the current page, so:
- In Theseus on bns://theseus.x/ the link resolves to bns://sirius.x/ —
direct BCNR, no gateway rewrite, no URL accumulation.
- On the silentmode.st ICANN mirror it resolves to https://sirius.x/ —
unchanged from the previous behaviour.
Only the four sibling .X hosts were swapped; silentmode.st, dl.silentmode.st,
code.silentmode.st, navigate.st, and every forge or API URL still carry
their explicit scheme.
Updates releases-manifest.json, releases/index.html, theseus/index.html
and site-theseus-x/index.html for the 0.3.78 release — the one with
the Ariadne plug-in toggle fix for 0.2.0 Just-me installs, the
Settings Middle East crash fix, covenant-held name resolution and
Pithos 0.3.16.
Two bugs the user hit while browsing the dev docs:
1. ariadne.x/dev/ used root-style hrefs ("thread", "dev", "assets/…") that
assumed the <base> tag workaround was active. On a client that walks
relative URLs against the page URL (BCNR direct hosts, Theseus in
gateway mode), every click appended one more segment — "/dev/plug-ins",
"/dev/plug-ins/extensions", etc. — because "plug-ins" resolved against
"/dev/" instead of the site root. Switched the dev page to proper "../"
relative paths (../thread/, ../assets/favicon.svg, ../#download) so it
resolves correctly regardless of host or base-tag presence. Same fix
on ariadne.x/thread/ (brand href="" went nowhere; the Product column
pointed every link at the current directory).
2. Theseus sub-pages had drifted apart. The home topnav was already
trimmed to Plug-ins · Extensions · Developers · Sirius.X · Get Theseus,
but plug-ins/, extensions/, brand/, and whitepaper/ still carried the
old "Brand" link in their topnav, had no "Developers" entry at all,
and lacked the mobile hamburger. Standardised all four to the home
pattern and dropped Brand + Whitepaper from the topnav on each page.
Both pages still exist and are reachable from the footer; neither is
on the top-level nav path.
Also added a Developers link + hamburger to ariadne.x/thread/ so the
Ariadne family matches the Theseus family on every page.
A developer / agent landing page on both .X sites so an LLM or a human
porting the resolver has everything in one place and does not need the
public gateway to understand how to talk to BNS.
ariadne.x/dev/ is the canonical page. Covers:
- Why: resolve names directly from the chain, with no operator in the
middle.
- BNS1 in one page: beacons, cash-token certificates, OP_RETURN payloads,
REG/UPD/REL, chipnet network constants, the six indexer rules
(including the 2026-10-04 one-message rule).
- The record-type table — u, h, a, ip, p, s3, tls, c, bl.
- A minimum viable resolver in under 100 lines of Node.js that pulls the
beacon's history, parses the OP_RETURNs, and prints a name's records.
- Pointers to every production implementation (Argus JS, Ariadne Kotlin,
the Windows Thread, the gateway) and every spec document on the forge.
- Public endpoints with a trust note: convenience, not consensus.
- Three paths for embedding Ariadne's Thread in your own app: chain-install
the Windows service, import the resolver library directly, or call the
local HTTP API; platform coverage table; MPL-2.0 licence note.
theseus.x/dev/ is a shorter page that cross-links to ariadne.x/dev/ for
the resolver work and covers Theseus-specific topics inline — the
extension publishing path (register a .x name on sirius.x, PUT signed
tarball to /api/ext, Theseus verifies the signature against the
on-chain owner before anything runs) and the first-party plug-in
surface.
Both pages are wired into the home-page topnav, mobile dropdown, and
footer Product column.
