An offer survives a reboot where the daemon starts at login, and says so where it does not: the listing's offer says whether it lasts across restarts or until this machine restarts and whether it came back after one, both clients say it in the same words and say the command once; a relayed approval offers only allow once and deny, since the laptop's rules are its own person's to loosen; the release keeps the versioned app archive alone, and the signing guide counts what a release signs¶
Decision 945 · accepted · 2026-10-25 · issue #58
An offer and a restart¶
Decision 928 made the offer outlive its client: the daemon keeps its own sign-in in the
operating system's credential store and, restarted, reads it back and offers again what its
record holds, with no client at all. What it left is the machine restarting. Nothing starts
the daemon after a reboot unless the person turned start-at-login on (troupe-daemon login
on, Decision 762); until a client starts it, the offer is offline. So the two cases are
told apart, and said:
- The listing says which. The offer a session's listing carries (
remoteinsession.listandsession.get, andremote.offer's answer) haslasts:across_restartswhere the login entry is there,until_restartwhere it is not. It is asked at each listing (Troupe.StartAtLogin.enabled?/1, which reads the entry's files and does not look for the binary), so turning start-at-login on after the offer is what the next listing says.restoredis true for an offer read back fromremote.jsonas the daemon started, until it is offered again. - Said once, with the command. The terminal's
/steer onanswer and the desktop app, as the offer is made, say one sentence wherelastsisuntil_restart: It stays offered until this machine restarts: troupe-daemon login on starts the daemon when you log in, and the offer comes back with it. Asked again,/steerand the desktop's Offered pill say only the state. - In the same words. The state is online (or connecting to the plane, offline
since …), then back after a restart and until this machine restarts where they hold:
/steersays (online, back after a restart), the desktop's pill Offered · Online · back after a restart.
Not chosen: the daemon writing the login entry itself at the first offer. It would make every offer survive a reboot, but a login entry is the person's choice (Decision 762 asks it in Setup, and the installers offer it), and a daemon that adds itself to the login items because a session was offered is the kind of thing a person finds later and did not agree to. Saying so, with the command, leaves the choice where it was.
Not done: the plane saying it. remote.list on another device says nothing of
lasts: the laptop's word is in its own listing, where its person reads it. Carrying it in
relay.offer is a field more on the plane's row and the brief's "no new relay method
beyond what idempotent re-offer needs" leaves it out.
A relayed approval offers what the laptop honours¶
Decision 921 decided it: a remote person cannot loosen the laptop's rules. An approval
answered from another device is allow or deny for that call, and allow_session, which
stops the session asking for the tool for the rest of it, is refused over the relay
(Troupe.Protocol.Relay) and is the laptop's person's to give at the laptop. Decision 928
repeats it for the terminal. Honouring it from somebody with control, recorded with who
allowed it, would undo that sentence, so the clients stop offering it instead:
- The terminal knows a session is a laptop's through the plane from the daemon's own
initialize(capabilities.relayed), which the worker publishes (relayed?) and the model keeps (Troupe.UI.TUI.Model.relayed?/1). The approval line reads (y allow once / n deny), the summaries y / n, the status line y/n approve once, and a delegation at the gate drops a always for …. Pressingasends nothing and says why: From another device a call is allowed or denied once: y allows it, n denies it. Allowing it for the rest of the session is done at the laptop. - The desktop app already left out the session-wide button on a relayed session; its allow button now reads Allow once, as the console's has since Decision 921.
-
The console's steering view offers Allow once and Deny, unchanged.
-
One app archive. The macOS build leaves an unversioned
Troupe.app.tar.gzof its own inbundle/macos/, whichKeep the installersuploaded with every*.app.tar.gz, so releases carried it besideTroupe_<version>_universal.app.tar.gz, named in the manifest, in nolatest.jsonand signed by nobody. The step that packs the updater's archive now removes any other archive first, and the upload names the versioned archive alone. The updater is unchanged:latest.json(scripts/release-desktop-update.exs) and the desktop app (release.rs) nameTroupe_<version>_universal.app.tar.gzonly.
Governs: apps/troupe_gateway/lib/troupe/gateway/remote.ex, apps/troupe_core/lib/troupe/start_at_login.ex, clients/tui/lib/troupe/client/steering.ex, clients/tui/lib/troupe/client/remote.ex, clients/tui/lib/troupe/ui/tui/model.ex