Did we do what we said?

One of part 1's eight roadmap items shipped, and it grew: accounts came with end-to-end encrypted sync instead of the plain Postgres sync we planned. The rest is still open, and most of this part's work came from using Solomon every day.

Accounts with end-to-end encrypted sync

Signed-in chats are encrypted in the browser before they leave it, so the server stores and syncs only ciphertext. Part 1 encrypted data on the server with a server-held key; now the server holds no key that can read a synced chat.

When you create an account you also choose an encryption passphrase, separate from your password. It unlocks a random account key, which unwraps a separate key for each chat. A recovery key is the only way back if you forget the passphrase. Resetting your password never touches your chats.

Sync runs on a self-hosted PowerSync service. Each device keeps a readable copy in IndexedDB and an encrypted mirror in local SQLite; uploads go through the Nest API, which checks that you own every row before writing it. Chats you made while signed out move into your account when you sign up.

Making it yours

Solomon now adapts to the person using it, and those choices follow you to every device.

• Six personalities. Balanced, Warm, Witty, Straight-shooter, Mentor and Curious change how replies sound, never what is true. The home screen changes with them: a greeting by your first name and the time of day, its own headline and four suggested prompts.

• Custom instructions. Up to 1,500 characters about you or how you want answers, added to every chat.

• Response style. Length (concise, balanced, detailed), formatting (plain, balanced, structured) and emoji on or off.

• Projects. Folders of chats with shared instructions, like "always give prices in yen" for a trip. Pin chats, move them between projects, and see a project's breadcrumb in each chat.

• Profile and My Day. A profile photo, your name and home city; My Day shows the weather where you live, your markets and news on the topics you follow.

Signed out, all of this stays in the browser. When you create an account, what you chose there carries over.

Images: three models, one rule

You can now pick the image model per request. Only one stays in memory at a time, because two would not fit in 16 GB alongside everything else.

The models run without content filters, because Solomon is also a tool for testing image models. One rule is enforced for every model and has no off switch: prompts that pair a minor with sexual or nude content are refused. We narrowed the check after it blocked harmless prompts like "a girl at the beach"; it now needs a clear sign of a minor, such as an age or "little girl".

Every generated image also lands in a new Library, next to the files you uploaded.

Everything around a reply

Part 1 was about getting a good answer; this part added what you do with it.

Every destructive action now uses a slide-to-confirm control: a half slide springs back, and keyboard users press Enter on the handle.

How it fits together now

Part 1 had one web app and one AI service; Solomon is now five services behind one gateway, ready to leave the laptop.

Accounts moved out of the Next.js app into their own small Hono service, so the web app no longer holds any auth secrets. It issues 15-minute signed tokens that the AI service, the Nest API and PowerSync verify on their own. Chat replies still stream straight from the AI service; Caddy passes them through unbuffered, and all services share one Postgres database.

What we learned

The biggest lesson this time: our own defaults can silently overrule the user. Rules like "lead with the answer, skip filler" made the model ignore "always call me Captain" in every test. Saying plainly that the user's instructions come first fixed most of it.

Two smaller lessons:

• Test the flow, not the parts. Every feature here was checked by a browser script that signs up a throwaway user, uses the feature end to end and deletes the user. Several problems only showed up there: the ignored custom instructions above, and a section picker that screen readers announced with no name.

• Encryption shapes features. Sharing, feedback and the library all had to answer one question first: what leaves the browser, and does the user know?

What's next Part 3 goes back to the answers themselves, and to leaving the laptop.

1. Recency-aware answers. Still the top item from part 1: prefer the newest sources and say when they disagree.

2. A server deployment. The gateway, auth service and sync are ready to run behind one domain with HTTPS; the models need a GPU box.

3. Reviewing reports. Feedback and reports are stored, but there is no admin view to read and act on them yet.

4. Files and images. OCR for scanned PDFs, and editing generated images.

5. Agents and tools. A calculator, database lookups and multi-step tasks in the LangGraph pipeline.