No description
Find a file
2026-04-02 17:55:30 +02:00
Agent add placeholder packages 2026-04-02 17:55:30 +02:00
Clam move to a UI package 2026-04-02 17:49:44 +02:00
ClamUI move to a UI package 2026-04-02 17:49:44 +02:00
journal add placeholder packages 2026-04-02 17:55:30 +02:00
OpenAIClient add placeholder packages 2026-04-02 17:55:30 +02:00
Tuist initial commit\nproject setup with tuist\nadd gitignore 2026-04-02 10:13:04 +02:00
.gitignore initial commit\nproject setup with tuist\nadd gitignore 2026-04-02 10:13:04 +02:00
AGENTS.md initial commit\nproject setup with tuist\nadd gitignore 2026-04-02 10:13:04 +02:00
mise.toml initial commit\nproject setup with tuist\nadd gitignore 2026-04-02 10:13:04 +02:00
Project.swift move to a UI package 2026-04-02 17:49:44 +02:00
README.md initial UI draft 2026-04-02 16:12:08 +02:00
summary-s1.md initial UI draft 2026-04-02 16:12:08 +02:00
Tuist.swift initial commit\nproject setup with tuist\nadd gitignore 2026-04-02 10:13:04 +02:00

Clam is a calm, local assistant with scoped continuity.

The main goal is trust through legibility: you should be able to understand how it works, what context it has, and why it answered the way it did.

The foundation is intentionally simple:

  • single user
  • single device
  • custom Swift UI
  • SQLite + FTS for storage and retrieval
  • AI-compatible API (ollama, openrouter) for inference
  • conversation search available to the assistant as a first-class tool from day one
  • filesystem and network access, but no extension ecosystem yet

The design principle is to avoid magic memory systems and instead rely on explicit containers, visible boundaries, and inspectable context assembly.