Built & Coming

What the Jellyfish Assistant is, and what it's becoming.

October 20, 2026

Open-source release

Local-first, free to self-host.

Planned

Hosted service

The same system, run for you; bring your own model keys.

Planned

Hosted inference

Optional private inference, and mobile apps.

Only the release carries a date. What follows it is intent, in order, with no dates.

Built

In the October 20 release.

Each card names the contract that describes it. Read them all.

Multi-provider backend

Local and frontier models side by side; you pick the model for each task and what each provider may see.

05

Encrypted at rest

Memory, credentials and logs encrypted under a key sealed to the machine; optional passphrase unlock; a printed recovery key.

01 §2.14–2.17 · 02 §2.10

Deletion that deletes

Deleted chats and turns are wiped from the file, the search index and the journal, not just hidden.

02 §2.11 · 07 §2.8

Sandboxing

Tool servers, memory modules and web pages each run sandboxed and reach only what they declare.

03 · 04 · 08

Quarantine

An add-on that reaches past what it declared is stopped and flagged to the owner.

04

One front door

One authenticated entrance for every client; every route declares who may use it.

08

Accounts and a second factor

Invites, an authenticator app or passkey on every login, recovery codes, device enrolment, idle lock.

06 §4.4–4.6

Roles and grants

Each person's role decides which tools, memory and pages they reach; nothing the system serves shows one person another's chats.

06 §4.8

Gates and a PIN

Any act can be gated behind your confirmation, and a PIN if you choose; destructive acts are gated by default.

06 §5

A watched way out

A per-tool allowlist by default, open-ended reach for tools you choose, and a log of every request.

06 §6

Semaphores

Conversations carry flags — outside content read, open-ended web access used — and outbound tools ask first once a chat is flagged.

06 §7

Tool servers

Capabilities discovered, enabled one by one, supervised, each with its own credential store.

04

Memory Core and modules

A small core with plug-in modules; each person's memory is its own file.

02 · 03

Chat history

Stored chats in three modes — Forgetful, Manual, Remember — with forks, sidebars and retention limits.

07

Slash commands

Type / to aim a message at a tool, switch modes, or open a sidebar.

08 §2.5.1

Credential isolation

Credentials go from disk to the process that needs them, never through the model.

01 §2.11

Modular web UI

Pages ship separately, arrive disabled, and are turned on one at a time.

08 §2.13

Voice

A hold-to-talk voice daemon on the host machine.

08 §2.11–2.12

First tools

Time, Spotify control, chat-history tools, capability management.

04

Public contracts

Nine contracts, published on the Architecture page with the release, to build on.

00

Coming

Intent, in no promised order.

Make it yours

A semaphore builder for your own flags and rules: "this chat has seen my finances, so no cloud model may read it."

  • Semaphore builder
  • Settings for each thing: what it can reach, and what can reach it
  • A better web UI with widgets
  • Setup wizard
  • App store for add-ons
  • Backups and migration

Everyday capabilities

  • Calendar
  • Contacts
  • Lists
  • Inventory
  • Email
  • News and research
  • Notifications
  • Alarms
  • Smart home
  • Media
  • Photos

The hosted service

The same system, run for you, with iOS and Android apps to go with it.

About the hosted plan →

Further out

  • The Overseer: optional background agents
  • Development suite
  • Project agents
  • Home and device presence
  • Wearables