v1.18.52

Added

• See what memory uses at the top of /memory, and change it from there. The Overview tab now
  opens with a Storage panel: on this computer (with the path, size on disk, and the model and its
  region), a database in Docker (with the container's name, image and whether it's running), a team
  database (host, jurisdiction and TLS; credentials are never shown, only the variable names they
  come from) or a managed cloud database (provider, region and whether your residency policy allows
  it). It shows the template that set it up and its live status. Change storage… opens the
  templates and storage cards and asks whether to move your facts or start empty. Move my facts
  counts them on both sides, and Start empty says where the old ones stay. Test connection
  updates "checked", Start container restarts a stopped Docker database, and Open in
  Settings goes to Settings › Memory. When your organisation sets the storage, the panel says so.
  lunos memory status prints the same block, and lunos memory storage set --template <name> or
  --backend <type>, with --move or --empty, changes it from a script.

• lunos sandbox doctor checks whether a sandbox can start on this machine. It lists each check
  (Docker or Podman installed and running, Linux containers, the git repository, the workspace mode,
  the image, and a throwaway test container) with pass or fail and, for a failure, what to do.

• When Lunos fails, it says where the full details are. Every run writes a log, and a failure
  (Lunos not starting, a failed /restart, a sandbox that won't start, a crash, an unexpected error)
  now ends with Full log: <path>, a clickable link in terminals that support it, and
  Report it: lunos bug-report <id>. The log has the full error with its causes, and each command
  Lunos ran with its exit code and output, so nothing has to be run again with extra flags. API keys,
  tokens and passwords are removed, and your prompts are never written to it.

• lunos logs and lunos bug-report. lunos logs lists recent runs; lunos logs <id> shows
  one, --open opens it, and --dir prints where logs are kept. lunos bug-report [id] packs a
  run's log with the version, the relevant config (secrets removed) and the sandbox checks into a zip you can check and
  attach to an issue yourself. Nothing is uploaded. In the TUI, /logs lists them, and an error
  about something running in the background (such as an MCP server that didn't start) has
  Open log.

• Log retention settings. Lunos keeps the last 10 runs plus failed runs from the last 14 days,
  within 50 MB. Change this with log.retention_days and log.max_mb; an organisation can lock it.

• A different tip every time. The home screen shows a new tip on each start, and a turn that
  runs for more than 3 seconds shows one line under the working indicator. Tips come from a deck
  shuffled for you, so none repeats until you've seen them all, and the same tip never shows twice
  in a row. There are now over 230 tips about Lunos itself: the Agent Monitor, the marketplace,
  memory, Claude Code and Codex sessions, language servers, sandboxes, your account and more. Tips
  only appear when they apply to you (memory tips once memory is on, nothing about a feature your
  organisation has turned off), and a tip shows your own key when you've changed a keybind. /tips
  lists every tip by category, searchable, with the ones you've seen marked; tips_next (unbound
  by default) shows another; "Hide tips" stays, and "tips": false in tui.json turns them off.
  Which tips you've seen is kept on your computer only.

Changed

• lunos shows its home screen about a second sooner. The screen and the prompt no longer wait
  for the local server, plugins or MCP servers: on a Mac a warm start now draws in about half a
  second instead of one and a half. You can type straight away; a prompt you send before Lunos is
  ready waits under the prompt ("Starting… your prompt is sent once ready") and goes out as soon as
  it can. The "Loading plugins…" box is gone: what's still loading shows as one quiet line at the
  bottom ("plugins loading · MCP connecting… (3)"), and MCP servers that didn't connect are named
  there for a few seconds. In a terminal that doesn't report its colours, start-up no longer waits a
  full second for it. To see where the time goes, run lunos debug startup, or start with
  LUNOS_STARTUP_TRACE=1.

Fixed

• Turning on the sandbox can no longer lock you out of Lunos. Before it's saved in /settings,
  Lunos checks that a sandbox can start here and refuses the change with the reason and the fix
  (for example "Docker Desktop isn't running — start it and try again"). If a restart after a
  sandbox change still can't start, the change is undone and Lunos starts as before. When the
  sandbox can't start, Lunos offers to start without it this time (unless your organisation
  requires the sandbox), and lunos --no-sandbox skips it for one start.
• A sandbox that can't start now says why instead of "Unexpected error". You see which step
  failed, the Docker command it ran (secrets hidden), its exit code and output, and a fix for the
  common cases: Docker not installed or not running, Windows-containers mode, WSL 2 missing, an
  image that can't be pulled, no network, or a port in use.
• Sandbox on Windows: Docker is found as docker.exe, and in Docker Desktop's install folder
  when it isn't on PATH yet; the repository is copied from drive-letter paths such as D:\work;
  mounted folders use paths Docker Desktop and Podman accept; and the command printed after a
  failed restart runs in PowerShell.

---

Last release: v1.18.51
Target ref: fd9e926

Core

Improvements

• 2149e02 bug-report includes the sandbox doctor checks; troubleshooting page points to the new log docs (@pminev1)
• f032171 Esc from Change storage… returns to /memory; shared lock rule; credential test positive control (@pminev1)
• de31407 the working line only draws a tip that fits; /settings sections validated (@pminev1)
• 6fa98f9 TUI draws its home screen before the server, plugins and MCP are ready (@pminev1)
• c573501 a different tip every time, from a deck of 239 Lunos tips (@pminev1)
• 8f8ea3f failures end with a link to a full, redacted run log; lunos logs and bug-report (@pminev1)
• b265b08 a sandbox that can't start says why, and never locks Lunos out (@pminev1)
• 6e703e6 Storage panel at the top of /memory, memory status block, memory storage set (@pminev1)
• ad3c373 sync release versions for v1.18.51

Bugfixes

• a3a45a1 repro test follows the sandbox error's new docker command and fix line (@pminev1)
• b9121c4 fix-first settings refusal, visible rollback notice, POSIX-only test guards (@pminev1)

TUI

• ba133cc keep tui.ts's lazy imports and worker env in the shape thread.test.ts checks (@pminev1)
• 8d0de80 keep the worker env built from process.env (thread test) (@pminev1)

Community Contributors Input

Thank you to 2 community contributors:

• @pminev1:
  • Storage panel at the top of /memory, memory status block, memory storage set
  • a sandbox that can't start says why, and never locks Lunos out
  • failures end with a link to a full, redacted run log; lunos logs and bug-report
  • fix-first settings refusal, visible rollback notice, POSIX-only test guards
  • a different tip every time, from a deck of 239 Lunos tips
  • TUI draws its home screen before the server, plugins and MCP are ready
  • the working line only draws a tip that fits; /settings sections validated
  • budget step runs even when unit tests fail; note plugin start timing
  • repro test follows the sandbox error's new docker command and fix line
  • Esc from Change storage… returns to /memory; shared lock rule; credential test positive control
  • keep the worker env built from process.env (thread test)
  • the session embed is dark Catppuccin on its own element, like app.lunos.tech
  • keep tui.ts's lazy imports and worker env in the shape thread.test.ts checks
  • bug-report includes the sandbox doctor checks; troubleshooting page points to the new log docs
  • changelog mentions the sandbox checks in bug-report
  • Release 1.18.52: changelog section
• @pminevp: