Skip to main content

Web interface

SvelteKit frontend with FastAPI backend. Sign in with Nextcloud, an email address and password, or a one-time email link, according to the deployment's enabled methods.

The web UI is per-user: each authenticated user sees only the features they have configured (feeds, money, location, etc.). Nextcloud login requires a configured user. Email login requires a live user profile and an enabled email identity, read from the database on each login.

Browser history​

Selections within a page appear in its URL and survive a reload or a shared link. Back and Forward restore the previous selection. Moving to another place adds a history entry; changing the year or date range replaces the current entry. Defaults and fallbacks also replace the current entry, so loading a list does not add a Back step. Free-text searches, display preferences and open overlays are not part of this history.

PageSelectionURL parameterHistory behavior
ChatRoomroomAdd an entry
ChatAll, Unread or Starred viewviewAdd an entry
ChatSearch result or task linkroom, taskAdd an entry
ChatCited messageroom, msgAdd an entry
BriefingsArchive itemidAdd an entry
BriefingsBriefing name filternameAdd an entry
FeedsFeed, category, Starred or Unread viewfeed, category, viewAdd an entry
Money transactionsAccountaccountAdd an entry
Money transactionsYear (all for All years)yearReplace the current entry
Admin logsLog sourcesourceAdd an entry
Health statsDate rangerangeReplace the current entry

Prerequisites​

  • A Nextcloud instance for Nextcloud login, or operator-created email identities for email login

The stack's image builds the frontend and its nginx fronts the web service, so nothing else is needed.

No extra Nextcloud apps are required — istota uses NC's built-in OAuth 2.0 provider.

iOS server discovery​

GET /istota/api/mobile/config is an anonymous, read-only compatibility endpoint for the generic iOS shell. It returns mobile protocol major 1, minimum app version 0.12.0, the /istota/ web base path and the versioned browser-handoff mode. All paths belong to the origin that answered the request. The response contains no account details, provider URLs or credentials, sets Cache-Control: no-store, and stays below 512 bytes. It never fetches an address supplied by a caller or changes a session.

This is the discovery part of the protocol. Browser approval, session exchange and the authenticated session receipt must also be deployed before distributing a generic binary that consumes it. Existing browser login and older iOS binaries continue using their current endpoints.

The installation needs device-trusted HTTPS, a configured public [site] hostname, and the existing /istota/ web prefix. Discovery returns 503 when no public origin is configured or that origin uses local plaintext HTTP. Host and forwarded-host headers cannot supply that configuration. The endpoint does not make the web build relocatable to arbitrary subpaths. Entering only an origin lets the app try /api/mobile/config and then the existing /istota/api/mobile/config after a 404 or 410.

An outer proxy must expose the compatibility endpoint without cookies, Basic Auth, a client certificate or its own login page. Those login walls are unsupported for generic setup; the installation's own browser sign-in can still use its identity provider. VPN/LAN access also needs working DNS/routing and a certificate iOS trusts, including an administrator-installed trusted CA where appropriate. Local-network permission is separate from certificate trust. The existing loopback-only no-auth and local-login-code restrictions remain in force.

location_ingest_path is /webhooks/location when the deployment enables location, otherwise null. The operator must route that path on the same HTTPS origin to the webhook receiver. This flag does not enroll a user, reveal an ingest token or override their location preferences; enrollment still requires an authenticated user and explicit consent.

push.delivery describes deployment configuration:

  • unavailable: push is disabled, automatic dispatch is off, or an APNs provider setting is missing.
  • direct: push and automatic dispatch are enabled, with a signing-key path, key ID, team ID and topic configured. Discovery does not read the key, contact Apple, check topic authorization or prove delivery. The daemon still needs its key file, HTTP/2 support and credentials authorized for the binary's topic.
  • relay: reserved for a future authorized relay; this server does not emit it.

A self-hosted operator must not receive the app publisher's APNs signing key. A generic app can connect without push; permission granted by iOS alone does not establish a delivery path. Use the existing operator push diagnostic to test APNs acceptance, which is still not proof that an alert appeared on the device.

Connection-bound push registration​

The generic iOS app (0.12.0 and later) adds connection_binding, a lowercase UUID, and connection_generation, a positive integer, to POST /istota/api/push/devices. Both are optional, but they are sent together or not at all. Older apps send neither and keep their current registrations and payloads. For a bound registration, every alert's istota routing object repeats both values, and the app does not open an alert whose values are not its current connection. Badge-only updates carry no routing.

The binding limits what a tap opens. It does not stop iOS from displaying an alert or applying a badge that an old server already sent, and removing a registration on the phone does not remove it from the server. If the app could not reach the old server when it disconnected, remove the device under Settings > Notifications on that server.

iOS browser sign-in​

The server supports browser approval and a one-use session handoff for mobile protocol 1. Deploy this compatibility work before distributing a binary that consumes it. Ordinary browser sign-in and older iOS clients retain their existing redirects when no mobile request is pending.

RouteContract
POST /istota/auth/mobile/requestsAnonymous JSON with challenge and state, each a canonical base64url 32-byte value. Returns request_id, authorize_path and expires_in: 600.
GET /istota/auth/mobile/authorize/{request_id}Requires a live request. Signs in through the existing login page if necessary, then displays the account and configured installation for explicit approval.
POST /istota/auth/mobile/authorize/{request_id}Requires live authentication and the approval form's CSRF token. Redirects to the fixed com.cynium.istota.auth://complete callback with only request_id, code and state.
POST /istota/auth/mobile/exchangeAnonymous form with request_id, code and verifier. Consumes the verifier-bound code, replaces all ambient session fields with a fresh ordinary session, and returns a 303 to /istota/auth/mobile/complete.
GET /istota/api/mobile/sessionRequires the handoff's live signed session. Returns {request_id, user_id} so a native client can confirm the exact exchange before enabling its bridge. An ordinary browser session is not a receipt.

The native POSTs accept at most 4 KiB, including streamed requests without Content-Length. Content type and any Origin are checked before reading; Origin must match the configured scheme, host and effective port. Duplicate or unknown fields, malformed encodings and invalid proofs are refused. These routes sit outside the API prefix: the existing guard still refuses ordinary anonymous API bodies without reading them. Responses are not cacheable, and no broad CORS policy is added.

The browser continuation is one request ID in the signed session, rechecked against its ten-minute database expiry after password, email-code, local-code or Nextcloud login. It is never an arbitrary return URL and never replaces OAuth state. Approval codes live for at most 60 seconds. Redemption rechecks account authority and consumes the code in the same SQLite transaction; concurrent exchanges have one winner. Replay returns 409, expired proof 410 and other invalid proof 400. Failed database access returns 503. A response lost after consumption does not make a code reusable: check the authenticated receipt, then restart sign-in if that receipt is missing or names another request.

The existing loopback host restrictions still apply to local-code and no-auth development installs. No-auth approval names the configured local user and still requires an explicit CSRF-protected action; an ambient local-mode API identity is not proof of a completed handoff. These route tests do not make plaintext localhost a supported discovery destination for the generic iOS app.

Email login​

Set [web] auth = ["email"] or ["nextcloud", "email"], provide a persistent session signing secret, and set [site] hostname to the public hostname. ISTOTA_WEB_AUTH=email or nextcloud,email overrides the config. Nextcloud remains the default regardless of the storage backend. Use HTTPS outside localhost.

Bootstrap the first administrator from the deployment shell, against the deployment's config and database:

istota init
istota user ensure alice --display-name Alice --email alice@example.com
istota auth add alice --email alice@example.com --print-link

Add alice to the admins file (/srv/app/istota/config/admins on a server, ISTOTA_ADMINS_FILE elsewhere) before inviting more users. With more than one user an empty allowlist makes nobody an admin, and the web admin pane requires an explicit entry in any case. Doctor fails this combination (security.admins, and web.auth.admins when multiple email identities exist). The printed enrolment link opens a password form and signs the user in on submission. Set a password for the first administrator so mail failure cannot prevent login. istota auth set-password alice prompts privately; --password-stdin reads one line for automation. There is no password argument on the command line.

The login page has password and email-code forms whenever email is enabled. Asking for a code opens a pending sign-in tied to that browser: the browser keeps a secret in its session, and the emailed 6-digit code works only together with it. The code is valid for 10 minutes by default and dies after five wrong guesses. Asking again from the same browser retires the earlier code only once a new one is sent, so a request over the mail budget leaves the last code working. Wrong codes are also capped at 20 per address per day across every browser, because anyone can ask for a code for any address; istota auth sign-in-code clears that cap. The mail carries no link, so opening it in another app or on another device changes nothing, and the iOS app's sign-in completes in the app. The code sits in the subject and on its own line, which lets Apple's one-time-code autofill offer it from Mail. Enrolment and reset links set a password and sign in on submission, with default lifetimes of seven days and one hour. Anonymous reset links and sign-in codes share a send budget of three mails per address per hour and return the same page for unknown, disabled and throttled addresses. Passwordless identities can sign in by code; they are not incomplete accounts.

Operator commandEffect
istota auth listProfiles and identities, password and disabled flags, last login, orphan status
istota auth add alice --email alice@example.comAttach email to an existing profile; add --create-user to create one
istota auth invite alice --sendSend an enrolment link
istota auth reset alice --print-linkPrint a password-reset link when mail is unavailable
istota auth sign-in-code alicePrint a fresh code for the newest pending email sign-in for alice's address, with when it was requested, for when mail is down. It works only in the browser that asked, and anyone can open a request for an address, so confirm the request time with alice before reading the code out
istota auth disable alice / enable aliceChange login availability and revoke existing sessions
istota auth logout-all aliceRevoke every session for an identity
istota auth remove aliceRemove login identity and invalidate its links; preserve profile and user data

Both link commands accept --send or --print-link; omitted means send. auth add has --send-invite and --print-link. Successful commands end with state=created, state=updated or state=unchanged; list always reports unchanged, and issued links and credential operations report updated. Identity changes are separate from inbound routing addresses.

The admin Users pane can create a profile, attach or change a login email (in the per-user editor described under User settings editor), send invitation and reset links, disable login and remove an identity. It has no action that sends a sign-in code, because a code only works in the browser that asked for it. It refuses disabling or removing the last enabled administrator identity, even with Nextcloud also enabled. The operator CLI remains the recovery authority and can override that protection. Disable blocks both email and Nextcloud login for that identity. Removing an identity blocks email login and revokes its sessions, but leaves Nextcloud login possible if that method is enabled. Nextcloud-only profiles have no per-user revoke or disable control until an email identity is attached. New users can sign in immediately, and the scheduler picks them up within one tick.

Settings has a Security card wherever email sign-in is enabled and the user has an email identity, whether they signed in by email or through Nextcloud. Password users supply their current password to change it; the change signs out every tab and device, including the caller. Passwordless users see a set-password link. Attaching an identity, changing its email or password, disabling it, and signing out everywhere revoke the user's existing sessions, including Nextcloud sessions. Epochs start with a random generation and then increase, so deleting and recreating an identity cannot revive old cookies. Removing an identity retains a session generation in web_auth_retired_epochs, so earlier Nextcloud and legacy cookies stay revoked; a fresh Nextcloud login uses that retained generation. Database read errors fail closed. Removing an authentication method rejects sessions minted by that method. Active streams repeat the checks and close after revocation.

Run istota doctor --only web.auth for method source, hostname, mail configuration, identity counts, admin allowlist, proxy IP throttle and session-secret checks. Mail configuration checks do not send a probe. The IP verification budget is inactive while web.trusted_proxy_hops is zero. A positive value selects the client address from the forwarded chain; only enable it when the backend cannot be reached around those proxies.

The shipped proxies suppress access logs for /istota/auth/set-password; both web launchers disable uvicorn access logs. An outer proxy must do the same or omit query strings, since the token grants access. Authentication pages are not cached and send no referrer. ["none"] is reserved for the direct istota serve loopback launcher without a public reverse proxy; The stack and direct uvicorn refuse it.

User settings editor​

Admin → Users opens a settings editor for one user: click the user's row, or pick "Edit settings" from its menu. A user you add from the same page opens in the editor once it is created. The editor sets the per-user fields that otherwise come from istota user ensure (or an inventory that runs it), so a new person can be set up without a deploy. It does not edit the admin list (the admins file), resources, secrets, or the preferences a user owns on their own /settings page, such as routing and default rooms.

The sections are:

  • Identity: display name and timezone. The admin badge is shown read-only.
  • Login: the current login email, its sign-in state and the last login, and a field to attach or change it. "Also add to email addresses" also lists the address for inbound mail, and "Send invitation" mails an enrolment link. The Login section saves with its own button, never with the footer Save. Invitations, password resets, signing out, disabling and removing the login stay in the row menu.
  • Email: inbound email addresses, trusted senders, quiet senders, and outbound approval. A value below the deployment's outbound_approval_floor is refused unless it is already stored.
  • Phone: the SMS number and the WhatsApp number, in E.164 form. "Same as SMS" copies the SMS number into the WhatsApp field. Below it are the WhatsApp enrollment state (Unbound, Waiting for first message, Enrolled, Opted out), the masked identity and when it was last seen. "Reset identity" keeps the number and forgets the enrolled phone, so the next message from that number enrolls again; use it when someone moves the number to a new phone. Changing an enrolled number discards the enrollment, the open service window and any opt-out. Each phone field is hidden when its surface is off, unless a value is already stored.
  • Access and limits: disabled modules and skills, the foreground and background worker limits (empty means the deployment default), and whether the default briefings are seeded. The last only matters when the user's briefings are first created.
  • Channels: the log and alerts channel tokens, read-only.

The footer Save sends only the fields you changed, and either all of them are written or none are. A refused field is marked with the server's reason.

Fields set by the deployment are locked. Every field an istota user ensure --managed call sets for a user shows "Set by deployment", cannot be edited, and is refused with 409 by the API. The user's own /settings page shows the same fields as "Set by your administrator". istota user ensure --name <id> --seed hands them back to the web UI. The Ansible management role passes --managed for a user whose inventory entry sets managed: true.

Addresses and numbers belong to one user. An email address, SMS number or WhatsApp number that another user already holds is refused, and the refusal names that user. An address counts as held when it is in another user's email addresses or is their login email. A duplicate stored before this check is not refused on resubmit, and istota doctor --only users.email_address_uniqueness lists any that remain. A user editing their own addresses on /settings gets the same refusal without the holder's name.

Changing the login email signs the user out. It ends every session the user has, including Nextcloud sessions, and voids any invitation or reset link already sent. The editor says so before you save. If sending the invitation fails, the new login email is still saved.

Saves take effect without a restart. The scheduler, the web app and the SMS webhook re-read user profiles within a few seconds of a change, so a new address or number routes mail and texts on the next scheduler tick.

The user is told. When an admin changes another user's email addresses, SMS number, WhatsApp number or login email, that user gets a notification, "An administrator changed your contact details", naming the fields and the admin but not the values. It goes through the user's normal alert delivery and closes once seen. Editing your own row raises nothing, and neither do changes to other fields.

Every admin save logs one admin_user_update line with the admin, the user and the field names, never the values. A refused collision logs admin_user_conflict with its kind (email, SMS or WhatsApp) and no value or holder.

Nextcloud OAuth2 setup​

1. Register an OAuth 2.0 client​

In Nextcloud, go to Settings > Administration > Security > OAuth 2.0 clients and add a new client:

FieldValue
Nameistota-web (or any label you prefer)
Redirect URIhttps://{your-hostname}/istota/callback

Nextcloud generates a Client ID and Client Secret. Copy both.

The redirect URI must exactly match the callback route. If you're running behind a reverse proxy at a subpath or different hostname, adjust accordingly.

2. Configure istota​

In your config.toml (istota setup asks for these when you connect a Nextcloud):

[web]
enabled = true
port = 8766
auth = ["nextcloud"]
oauth2_provider = "https://cloud.example.com"
oauth2_client_id = "your-client-id-from-step-1"
oauth2_client_secret = "" # or set ISTOTA_WEB_OAUTH2_CLIENT_SECRET env var
session_secret_key = "" # or set ISTOTA_WEB_SESSION_SECRET_KEY env var
SettingDescription
oauth2_providerYour Nextcloud URL (no trailing slash) — what the browser hits to authorize.
oauth2_client_idThe client ID from the OAuth 2.0 registration.
oauth2_client_secretThe client secret. Prefer the ISTOTA_WEB_OAUTH2_CLIENT_SECRET env var.
session_secret_keyRandom string for signing session cookies. Generate with python3 -c "import secrets; print(secrets.token_hex(32))". Use the ISTOTA_WEB_SESSION_SECRET_KEY env var in production.

Optional overrides (defaults derive from oauth2_provider):

SettingDescription
oauth2_token_endpointServer-to-server token URL. Set it when the stack reaches Nextcloud at a different address from the one browsers use (the wizard's Nextcloud URL and public URL).
oauth2_userinfo_endpointServer-to-server userinfo URL. Same case.
oauth2_redirect_uriExplicit redirect URI override; otherwise derived from request host + scheme.

The two secrets are files under /srv/app/istota/secrets/ (istota_web_oauth2_client_secret, istota_web_session_secret_key), which the stack exports as those environment variables, keeping them out of the config file.

3. Restart​

Restart the stack (istota-stack down && istota-stack up). The web app is the stack's web service, built into the image with the frontend, and its logs are istota-stack compose logs -f web.

The stack's nginx is the only listener, and it already routes /istota/ and keeps /istota/auth/set-password out of its access log. A reverse proxy of your own in front of it (proxied ingress) forwards the whole hostname, and needs the same access-log exclusion for /istota/auth/set-password, or no query strings in its logs. It should also cap request bodies on /istota/login/email and /istota/auth/ at a few tens of kilobytes, as the stack's nginx does (32k), because those forms are posted without a session. See Ingress and TLS.

TLS is required — session cookies are set with secure=true and the registered redirect URI must use HTTPS. direct ingress gets a certificate from certbot; proxied takes it from your proxy.

How Nextcloud authentication works​

  1. User visits https://{hostname}/istota/ and is redirected to /istota/login
  2. Istota redirects to Nextcloud's OAuth 2.0 authorization endpoint ({oauth2_provider}/index.php/apps/oauth2/authorize)
  3. User authenticates with their Nextcloud credentials (or is already logged in)
  4. Nextcloud redirects back to /istota/callback with an authorization code
  5. Istota exchanges the code for an access token; NC inlines user_id in the token response, so identity is known without a second round-trip
  6. Token retention follows web.token_storage: ephemeral discards it; encrypted retains it with the web-only token key. The cookie carries the user and authentication method/epoch.
  7. If the username exists in config.users (or auto-seeds a user_profiles row), a signed session cookie is set (7-day expiry)
  8. Subsequent requests validate the session method and any attached email identity, including its disabled state and credential epoch

If the token response doesn't include user_id (older NC versions or custom auth backends), istota falls back to fetching identity from the OCS userinfo endpoint with the bearer token before discarding it.

Users not in the config are rejected with a 403 even if they have a valid Nextcloud account.

A callback that fails does not 500. A state mismatch or a declined authorization renders a login-shaped error card with a 400, and an unreachable provider a 502; the card never echoes provider- or exception-derived text back to the browser. Logging out is confirmation-gated in the UI — the logout and menu icons sit side by side and are small on a phone, so a mistap used to end the session and send you back through the login screen.

A light/dark theme toggle in the shell header switches the whole UI between themes; the choice persists per browser.

Installing to a home screen​

The UI ships a favicon, an Apple touch icon and a web app manifest, so adding it to a phone's home screen gives the Istota mark rather than a screenshot of the page, and the browser chrome takes the colour of the theme you picked in the app rather than the system's. A service worker is registered only inside the iOS shell, where it is what lets a cold launch with no connection reach the cached rooms and transcript; SvelteKit's own registration is off (kit.serviceWorker.register = false in svelte.config.js) and routes/+layout.svelte registers it behind isNativeShell(). An ordinary browser gets none of it, deliberately: hashed assets are cached for a year and everything else revalidates, so a continuously deployed app can never leave a browser pinned to a shell whose chunks the server has since deleted. See web chat for what the app keeps and how to clear it. When a new build lands, a toast offers a Reload rather than reloading under you — it also re-checks when you return to the app, since a suspended one stops polling.

The manifest asks for a portrait orientation. The layout is a single column with a docked composer, and landscape leaves too little height once the keyboard is up. That request only binds an Android home-screen install: iOS ignores the manifest key (the native shell locks iPhone to portrait itself, and leaves iPad free to rotate), and an ordinary browser tab cannot be locked at all.

The app bar​

A notification bell sits in the app bar on every page, not only in the chat. The badge counts what is open — a task held for your approval, a reply held at the outbound gate, a scheduled job that switched itself off, a credential the remote rejected, a bloodwork panel left in draft, or a one-shot alert. Clicking it opens a panel with an "All" and a "Needs action" tab, carrying the same Confirm and Discard buttons the chat cards have. An answer given on any surface closes the item on all of them. See notifications and the inbox.

Pages​

Chat: an always-on, full-page in-app chat console — the first nav tab, before Feeds. Discord/Slack-style rooms in a sidebar, live SSE streaming of tool use and intermediate text, !commands and the !model prefix, confirmation cards, attachments (drag, paste, the + button, or a voice message), clickable attachment chips, and per-message copy / star / delete. Email thread rooms render each message as a mail card, are read-only, and sit in a collapsed "Email threads" group under the room list. See Web chat for the full surface.

Dashboard: shows available features for the authenticated user. When Google Workspace is enabled, users link their Google accounts from Settings → Connections. Admin → Connections has a Google Workspace card with configuration status, the callback URL and allowed service access. Its Configure action opens the Google fields in Admin → Configuration; the card reports loaded settings, without testing credentials or connecting a user's account.

Feeds: RSS feed reader with masonry card grid, image/text filter, sort-by dropdown (published/added), grid/list view, navigable image lightbox, and a click-to-expand reader overlay that shows a card's full un-clipped content with ←/→ navigation between posts and an "Open original" link. The sidebar scopes the view to all, unread, an individual feed, or a whole category (click a category name to filter to it); the Unread and Starred views show their totals, and a feed with unread entries is bold and marked. Per-entry starring (f keyboard shortcut) and scope-aware bulk mark-as-read (Shift-A / toolbar button) honor the active feed or category scope. Viewport-based read tracking marks entries as read after 1.5s visible. Repeat images are suppressed as a reblogged photo travels through the blogs you follow: a duplicate inside one post is dropped, and across posts an image a newer entry already showed is hidden on the older ones (the post still appears, with a note counting the hidden repeats). Suppression is bounded to a recent look-back window and to the view you are in, so an image resurfacing much later still shows and browsing one blog never hides a tile because of another. Video embedded in a post plays inline with normal controls; nothing autoplays, and the image/text filter hides inline video along with pictures. Sprocket-icon settings page for managing subscriptions, categories, OPML import/export, and the repeat-image look-back window (switchable off). Served by the in-tree istota.feeds module against per-user SQLite. See Feeds. Requires the feeds module to be enabled (on by default).

Briefings: reader landing page for generated briefings with an archive sidebar (per-result kebab → delete) and a name filter in the header, plus a settings page (cog) for editing a briefing's content blocks and their sources, its schedule, and its delivery target. Source paths use a searching file picker with an advisory existence check. Admins additionally get a "Shared blocks" card for the module-owned blocks every user can read. Requires the briefings module to be enabled (on by default).

Money: accounting dashboard with ledger queries, transaction management, and reports. The Business section is Work | Invoices: Work is a full CRUD surface over the work log (entries addressed by stable id, with per-entry etags so a concurrent agent edit conflicts rather than being silently reverted), and Invoices generates, voids and creates invoices and previews their PDFs. Money Settings → Invoicing is the CRUD surface over the invoicing config — clients, entities and services — so nothing about invoicing needs the CLI. Backed by the in-process money module (no external service); also covers quarterly tax estimates and portfolio tracking. See Money. Requires the money module to be enabled (on by default).

Admin: read-only system health (task counts by source, worker pool, per-module DB stats, models pane showing the active brain and its resolved role tiers). A banner surfaces a degraded primary brain — when the availability breaker is open, automatic work is being skipped or routed to the fallback. Gated by the admins file, which fails closed when empty.

A Claude Code subscription card carries the plan's rate-limit windows — a tile per window, tinted by the configured warn and high thresholds, plus an Extra usage tile where pay-as-you-go credits are enabled. It is the budget the cost column below it cannot report, since pricing plan tokens at list rates would be inventing an invoice. A footer gives the reading's age and, where the last fetch failed, the error behind the stale number. The card is absent rather than showing an error when there is no reading to draw — on a deployment that cannot use the subscription it never polls at all. See the subscription reading.

A Token usage card carries 24-hour and 30-day totals, the cache hit rate, and average initial and peak context, then breaks the 30-day window down by model, by brain and by origin. Per-user tokens and cost sit on the Users rows beside that user's task counts rather than being repeated here, so the two copies cannot disagree. Cost is shown as currency only where it is real charged spend; a plan-equivalent or a catalog estimate renders as a dash. Two honesty counters sit alongside: how many tasks in the window recorded no usage at all, and how many rows recorded no context measurement. The card renders on its own — a database that has not yet been upgraded with the usage table takes out that section alone rather than blanking the dashboard. See token usage and cost.

A Browsers page lists each live browser instance (user, slot, idle time). It refreshes every ten seconds and never starts a browser or keeps an idle one alive, so only browsers already running appear. View opens that user's display in the page, after the admin confirms with their password or a mailed code, and the admin can watch it or work it with mouse and keyboard; View only stops input. The address is /istota/admin/browsers?user=<id>, so Back returns to the list. A console closes after an hour, and when the admin's credentials or admin rights change. Behind your own reverse proxy, the proxy must forward websocket upgrades; see Websockets through a reverse proxy and browser profiles.

"Last active" in the user list counts only interactive tasks. Scheduled jobs, briefings and module pollers do not move it, so someone whose only traffic is automated shows a dash. Their task total still counts everything.

Health: body stats grid with sparklines, labs matrix (dates × markers with flag-colored cells, a specimen filter, CSV import/export), panel detail with inline edit and source preview, per-marker trend charts with out-of-range zones and LLM explainer, medical history timeline with encounters and diagnoses, immunization tracking with coverage status strip, vaccine drill-down pages with clinical explainers. Garmin Connect (daily-summary sync) is on the general Settings → Connections page, shared with Location. Requires the health module to be enabled (on by default).

Location: today view (current position, day summary, trips), history (date picker, activity filter, heatmap), places (discover clusters, create/edit/delete, visit stats). Requires GPS tracking to be enabled.

Settings: a sidebar of up to ten sections — Account (identity, profile picture, sign-in), Preferences (appearance, unread marks in the navigation, email senders, disabled skills and modules, the quick notes folder, offline data), Notifications (see notifications), Delivery (default destination, relay questions, alert and log routes), Credentials, Wallet (see wallet), Scheduled jobs (your jobs, their last runs and what each may reach; see scheduling), Assignments (for an admin; see assignments), Connections (Nextcloud, Google Workspace, Garmin, Karakeep, ntfy, connected mail accounts) and Devices (each phone once, with what its tokens can do, and one Revoke for all of them; see location) — plus the per-module settings pages. Connections is where service credentials are entered — write-only, bullet-masked fields backed by the encrypted secrets store. With [web] token_storage = "encrypted", its Nextcloud card also lists the user's calendars and address books and shares each with the bot at No access, Read-only or Read and write, sent with the user's own token; see Nextcloud. Credentials lists every credential a task can use, with its bound hosts and the grant that decides which rooms and scheduled tasks may use it, edited from each row's menu. The credential vault card sits on that section too, and is the one surface a user sets one up from: it lists the .kdbx files in their own vault folder, takes a filename rather than a path, generates the passphrase, and names the shared credentials istota holds from the file.

API routes​

RoutePurpose
/istota/loginEnabled login methods, password and email-code forms
/istota/login/emailPassword sign-in (POST)
/istota/auth/sign-in-code/requestRequest an emailed sign-in code for this browser (POST)
/istota/auth/sign-in-codeEnter the code (GET/POST)
/istota/auth/resetRequest a password-reset link (GET/POST)
/istota/auth/set-passwordEnrolment or reset form (GET/POST)
/istota/auth/localThe Mac app's one-use login code, read from the URL fragment (GET/POST; local_code only)
/istota/api/account/passwordChange password and end every session (POST)
/istota/api/admin/usersList or create profiles and email identities
/istota/api/admin/users/{user_id}One user's settings (GET, PATCH); remove an email identity (DELETE); action suffixes: invite, reset, disable, logout-all (POST)
/istota/api/admin/users/{user_id}/identityAttach or change the login email (PUT)
/istota/api/admin/users/{user_id}/whatsapp/resetForget the enrolled WhatsApp identity, keeping the number (POST)
/istota/api/admin/briefingsEvery personal and group briefing's definition and state (GET); /{kind}/{id}/hold and /resume (POST) and /{kind}/{id} with the typed name and a step-up proof (DELETE), where kind is personal or group
/istota/callbackToken exchange + identity resolution
/istota/logoutSession clear
/istota/api/meUser info + features
/istota/google/connectGoogle OAuth initiation (separate, for the gws skill)
/istota/google/callbackGoogle OAuth callback
/istota/api/google/statusGoogle connection status
/istota/api/google/disconnectRemove Google tokens
/istota/api/feedsNative feeds module (per-user SQLite)
/istota/api/money/*Money module (ledger, transactions, invoicing, work entries, invoicing config)
/istota/api/briefings/*Briefings module (reader, archive, blocks/sources editor, shared blocks)
/istota/api/location/*Places CRUD, pings, trips
/istota/api/health/*Stats, panels, biomarkers, encounters, diagnoses, immunizations, Garmin sync, settings
/istota/api/garmin/*Garmin connected-service auth (status, connect, MFA, disconnect) + GPS track import; shared by Health and Location
/istota/api/chat/configChat limits + streaming intervals
/istota/api/settings/*Per-user preferences, connected services, per-module settings
/istota/api/settings/nextcloud-sharingThe user's calendars and address books at the bot's share level (GET); set levels, judged by a re-read (PUT)
/istota/api/settings/nextcloud-tokenDisconnect Nextcloud (DELETE); ?unshare=true removes the bot's shares first and keeps the token if any remain
/istota/api/admin/*Admin dashboard aggregates (stats, logs, config view) — allowlist-gated
/istota/api/chat/roomsRoom CRUD (list/create); PATCH /chat/rooms/{id} renames and changes per-user settings, listed among them (an email thread only; any other room is 400); DELETE hard-deletes
/istota/api/chat/rooms/{id}/promoteCreate a Talk conversation for a web-origin room and bind them, or replace a binding whose conversation was deleted
/istota/api/chat/rooms/{id}/read · /chat/rooms/read-allMark read cursors
/istota/api/chat/rooms/{id}/messagesMessage history + send. A send into an email room is 409 read_only. A send may carry about_room: <token> to link the turn to an email thread with no note to reply to; a link that fails its checks is 400 and creates no task
/istota/api/chat/messagesCross-room message query
/istota/api/chat/messages/{id}/star · DELETE /chat/messages/{id}Star / delete a message
/istota/api/chat/stream · /chat/eventsRoom-level event stream and snapshot
/istota/api/chat/commandsThe !command catalogue for the composer
/istota/api/chat/filesFiles shared into chat
/istota/api/chat/tasks/{id}/streamSSE stream of a task's events (tool use, text deltas)
/istota/api/chat/tasks/{id}/eventsSnapshot of a task's events
/istota/api/chat/tasks/{id}/confirm · /cancelConfirm / cancel a chat task. Confirm takes an optional {"room": <token>}; a relay question, room post or guest proposal needs the private room showing its preview
/istota/chat/r/{room} · /istota/chat/r/{room}/t/{task}Deep link from a notification: redirects to that room (and task) for a member, else to the chat page
/istota/api/chat/attachmentsAttachment upload (multipart, one file per request)
/istota/api/chat/voiceThe iOS app's voice task: one recording (multipart file and client_msg_id) sent into the user's default room as an attachment-only message. Takes the session or a device token with the voice scope; a retry under the same key answers 200 with replay: true and stores nothing
/istota/api/workspace/filesOne text file in My files for the Files editor (GET); save it against the revision it was read at (PUT). A changed file is a conflict, not an overwrite
/istota/api/workspace/notesCreate a quick note in the quick notes folder (POST; the session or a device token with the notes scope; a retried client_note_id replays the stored path); replace one (PUT; session only)
/istota/api/devicesEvery phone holding a credential for the user, once each, plus location trackers (GET); mint or replace this device's token, returned once (POST); DELETE /devices/phones/{device_id} revokes every token a phone holds, DELETE /devices/{id} one token, and DELETE /devices/self the calling device's own, on its bearer alone
/istota/api/notifications/countBell badge: {"open": N, "actionable": M}. Plain SQL, no resolver pass — the layout polls it every 30s from every route
/istota/api/notificationsThe panel's rendered rows plus total_open; ?filter= and ?limit=
/istota/api/notifications/{id}/dismissClose one row. Another user's row is a 404, never a 403
/istota/api/notifications/seenMark rendered rows seen. The body carries (id, updated_at) pairs, so a row bumped between the fetch and the POST is stamped but not closed
/istota/api/map/basemapThe resolved map tile spec for this user — style URLs and attribution, never a bare key. Reads the same resolver as doctor's web.basemap check, so the check cannot pass while the map is blank. See [web.map]

The SvelteKit build is served as static files for all other /istota/* paths.

Deployment​

The image builds the frontend. The web app runs as its own compose service, web, beside the scheduler's daemon.