Files
Skald-Circle/agents
dguiducci 080ea736e4
Nightly Build / build (push) Successful in 7m38s
feat: signpost the virtual memory roots inside the container, instead of leaving them absent
`user-memory/` and `shared-memory/` live in SQLite, so nothing of them existed on
disk — and that nothing was worse than it looks. `cat user-memory/x.md` returned a
bare ENOENT, which a model reads as "the note is missing" rather than "wrong door";
and `mkdir -p user-memory && echo … > user-memory/x.md` *succeeded*, writing a real
file into the home that no reader ever visits (every reader goes to `memory_docs`)
and that the next `ls` then confirms as if it had worked.

Each root now gets a read-only bind mount holding a README that names the tools to
use instead. Read-only as a mount rather than as a mode: the container user has
passwordless sudo, so a chmod would be a suggestion, while `:ro` holds — remounting
needs CAP_SYS_ADMIN. Verified in a scratch container: write, sudo write, sudo chmod,
sudo mount -o remount,rw and sudo rm all fail. And a README rather than an empty
directory, because "Permission denied" is an error, not an instruction — models
answer it by reaching for sudo; the README puts the correction in the same directory
the failing command just named.

The mounts are deliberately not part of `UserFs`: they back no agent path and the
host-side fs-tools must never resolve into them. They reach existing containers as a
fourth self-heal axis in `reusable()`, not as an IMAGE_TAG bump — the image is
unchanged, and a bump would make every installation rebuild it to fix a mount.

The matching half is in `classify_memory`, which now strips the home spellings
(`./`, `~/`, `/root/`) before matching the root. Without it `~/user-memory/x.md`
missed the match and fell through to the disk router — becoming exactly the
invisible physical file the signpost exists to prevent.

`agents/common/memory.md` says the rule outright: the stores are reachable only
through the file tools and `memory_search`, never through `execute_cmd`.
2026-08-02 22:34:24 +01:00
..

Agent icons — style guide

Each agent in the agents/ directory can have an icon/avatar declared in the "icon" field of its meta.json. The backend serves the file via GET /api/agents/{id}/icon.

Visual style

Icons are generated with Vector Paintings LoRA via ComfyUI in a warm, family-friendly style:

  • Style: painterly vector — bold shapes fused with expressive brushstrokes
  • Technique: vivid colours, emotion, motion, warm lighting
  • Format: square (1024×1024), rendered as a character portrait
  • Background: warm, cozy, medium-bright (no dark/no neon)
  • Subject: a warm animal character representing the agent's role, with contextual elements (tools, symbols, objects)
  • Palette: terracotta, amber, warm gold, coral, soft teal — warm and inviting
  • Trigger word: VectorPaintDaal must be included at the start of the prompt

Prompt template

VectorPaintDaal. A warm friendly {ANIMAL} character with a gentle smile, wearing {CLOTHING/ACCESSORIES}. It holds {OBJECT} and around it float {SYMBOLS}. Warm golden light, cozy atmosphere. {DOMINANT_COLOURS} palette. Expressive bold brushstrokes, painterly vector style. Family-friendly illustration, portrait of a kind {ROLE}.

Per-agent reference

Chat agents — warm animals

Agent Animal Role Elements Palette
Main Assistant 🦊 Fox General assistant Glowing threads connecting a heart, star, house Terracotta, amber, gold
Project Coordinator 🦡 Badger Family coordinator Floating threads linking heart, star, house, smiling face; cozy kitchen table Terracotta, amber, gold, coral
Researcher 🐿️ Squirrel Curious researcher Glowing book, magnifying glass, compass, scrolls, stars Terracotta, amber, soft teal, coral
Generalist 🦫 Beaver Handy executor Glowing multitool, wrench, paintbrush, trowel, cooking pot Terracotta, orange, amber, timber
Code Explorer 🕵️ Meerkat Curious analyst Magnifying glass, data trails, sparkling code symbols Terracotta, amber, deep blue, gold
Software Architect 🏗️ Heron Thoughtful planner Floating blueprints, geometric shapes, building blocks Terracotta, soft teal, amber, pale gold
Software Engineer 🔧 Bear Focused builder Glowing wrench, gears, circuit board, hammer, sparks Terracotta, orange, amber, steel grey
Spec Writer 📝 Owl Wise scribe Glowing quill, scrolls, open books, words floating mid-air Deep indigo, burnished gold, amber, cream
Tech Lead 👑 Stag Confident strategist Holographic kanban board, task cards, sub-agent symbols Warm amber, deep teal, gold, coral
Business Analyst 💼 Magpie Thoughtful evaluator Glowing clipboard, floating documents, abacus, data points Deep indigo, gold, soft teal, amber
Companion 🦦 Otter Children's friend Glowing pencil, smiling sun, star, open book, paintbrush Soft coral, amber, gold, gentle teal

System agents — insect family

System agents (type: "system") are invisible background agents that maintain the platform. They use insect characters to visually distinguish them from chat-facing agents.

Agent Animal Role Elements Palette
Event triage 👁️ Spider 🕷️ Watchful guardian Sensor nodes, glowing web, radar arcs, notification symbols (bell, letter, calendar) Dark purple, amber, soft cyan, warm grey
Private Memory Lint 🧹 Firefly Private memory caretaker Glowing lantern, memory fragments, tiny notes, sparkles Warm gold, amber, soft teal, gentle green
Shared Memory Lint 🧹 Bee 🐝 Shared space caretaker Scroll with guidelines, honey dipper, honeycomb shapes, tiny documents Warm amber, gold, soft teal, honey

Adding a new agent icon

  1. Generate the image using the Vector Paintings prompt template above (include VectorPaintDaal at the start)
  2. Save it as agents/{agent_id}/icon.png
  3. Add "icon": "icon.png" to the agent's meta.json (if not already present)
  4. No code changes needed — the backend serves whatever file path is declared in the manifest