Files

T

Nightly Build / build (push) Successful in 5m36s

Details

feat(files): a Files section over the caller's whole space

Until now file browsing existed only inside a project, and the two memory
stores were reachable only by the agent's tools. `#files` is the general
surface: home, both memory stores, the shared folders and projects the
caller belongs to, plus the read-only skills and docs trees.

The root is virtual, and that is the design. Anchoring at `~` is wrong:
the explorer reads host-side, while `shared/`, `projects/`, `skills/` and
`docs/` are bind mounts inside the container — a page rooted at the home
would show less than the user has with no way to reach the rest, and on
native Linux would show Docker's empty mountpoint stubs, a door that
appears to work and leads nowhere. So level 0 is a synthetic list from the
new `GET /api/files/roots`, serialized from the caller's `UserFs` plus the
two virtual memory roots. It sends `kind`, never a label: labels are copy
and get translated.

`GET /api/files/dir` now answers `{ path, can_write, entries }`, and a
memory path is classified before `resolve_view_path` (which refuses one)
and listed from `memory_docs`: one level derived from the flat key space
by the pure `memory_docs::immediate_children`, over a single query whose
unslashed prefix also spots an exact note as "not a directory". Memory is
read-only from the page — every writer routes through `resolve_view_path`,
and `shared-memory/*` is `@fs_write require` for the agent, so a button
that walks past that rule is a decision of its own.

The explorer moves out of projects into `shared/file-explorer.js`, taking
`root` + `rootLabel` and reading `can_write` from the listing rather than
from its host: writability changes per branch and comes from the same
`UserFs::can_write_to` the server rejects writes with, so the buttons
offered and the writes accepted cannot disagree. Deep-linking needed it
steerable without a two-way binding, hence `rel` in and
`explorer-navigate` out — the event fires only for a click, never for a
`rel` the host set, so echoing it back is a no-op.

The URL carries the agent path of the open folder in one parameter, the
same vocabulary the assistant uses, so a link is shareable and pasteable
into a conversation; which root it belongs to is derived, not stored.

docs/: a new files.md, plus two pages this made false — shared-folders.md
claimed in three places that a shared folder has no explorer, and
memory.md never said a user can now read their own notes.

2026-08-22 20:09:56 +01:00

4.5 KiB

Raw Blame History

Changelog

All notable changes to Skald Circle are recorded here, newest first.

The format follows Keep a Changelog. Versions are the workspace Cargo.toml version — the one ci/verify-version.sh checks before a release PR may merge — and a section is closed at the commit that bumps it.

[Unreleased]

Added

A Files section in the menu: everywhere you can reach, in one place — your home, your personal and the shared memory, the folders and projects shared with you, plus skills and documentation. Browse, open, download a folder as a ZIP, and upload, rename or delete wherever you have write access; the read-only places say so. Your memory notes are readable here for the first time (changing them still goes through the assistant).
Several conversations per source: open extra chats with +, and the tab bar you left open is restored at your next login, on any device.
A background task now reports back into the chat that started it instead of only the Inbox, and a chat shows the tasks still running under it.
Skills reworked for the multi-user model: a shared tree plus a per-member one, with a generated index injected into the agent's prompt.
The agent is told what its sandbox can actually run, from a probe of its own container.
Event triage can be tuned per person: a check interval that overrides the instance one, and notification preferences read from user-memory/notifications.md.
The assistant now remembers how you like emails and documents written — preferred wording, openings, sign-offs, formal vs. informal, per-recipient exceptions — as a short section of your private user.md, and applies it to later drafts.
File viewer: syntax highlighting for code files and for code blocks in the chat, a hover copy button on those blocks, and history browsing for a file under git.
Project explorer: download a folder as a streaming ZIP.
Collapsible icon-only sidebar on desktop.
DeepInfra, as a declarative LLM provider.
The project coordinator offers to keep a history of a project.
An agent can ask which connectors it holds instead of guessing.

Changed

Runtime image v4: Debian 13 base, plus the shared libraries a headless Chromium needs.
Unencrypted users are unlocked and their runtimes started at boot, so Telegram, cron and the background agents work after a restart without anyone opening the web app first.
PDFs render through pdf.js instead of an iframe.

Fixed

The server keeps running after you log out of the box; the install / update / uninstall scripts were hardened alongside it.
Skald survives a restart of the Docker daemon.
A user database gets the owner schema re-applied when it is opened.
An approval bypass applies to the tool it was granted for, not to its whole connector.
Connectors: an admin can use the ones they implicitly hold, per-user ones appear in the security-group picker, one whose process died is brought back, a global one's dependencies are installed where they are needed, and the prompt's connector list is rebuilt when the set changes.
Telegram: pairing codes are no longer burned on the way out nor handed out unrecorded, and send_attachment resolves paths in the user's own workspace.
The notification home is stored in the owner's database instead of the registry, where it silently dropped every batch it built.
Event triage no longer notifies you about the messages your preferences told it to filter — a filtered event now produces silence rather than a notification explaining that it was filtered.
LLM calls send the provider's model id on the wire rather than the local alias, and catalog capabilities resolve for reasoning-mode queries.
get_ast_outline runs in the caller's workspace, gives a markdown heading a section range instead of a single line, and shows a proper name and icon on its chat card.
The re-login dialog no longer hijacks the login screen, the new-chat + menu is visible and clickable, and the session-detail page stays live instead of freezing on a snapshot.
A silently dead agent WebSocket is detected and redialled.
A generated image lands in your own workspace instead of a server folder nobody could reach, so the assistant can finally send it to you on Telegram, open it in the viewer, or work on it with a command. It still shows inline in the web chat, its file is named after the prompt, and it is now readable only by the person who asked for it.

Releases up to and including 0.2.0 predate this file; git log is the record for them.