Sundial Try the demo

A local memory of your work, for you and your coding agent.

Here is everything it keeps on your Mac, and the little that can leave.

Try the demoInstall in a minute

What stays and what leaves

Stays on your Mac

One file, ~/.sundial/sundial.db, readable only by you.

On from the start

  • Front windowApp name, window title, the open document’s path
  • CalendarEvent titles, times, attendees, organizer
  • Browser tabSite and path of the front tab, and its title. Never the query string
  • GitBranch, last commit subject, changed-file count, commit sizes
  • Files and functionsWhich files change in your projects, and the function names touched
  • ShellCommands you run; with the hook, also folder, exit code and duration
  • Coding agentThe folder and branch of your Claude Code sessions. Only those two fields
  • Pull requestsNumber, title, state, review and check status, via your own gh
  • Input activityHow many key presses, clicks, moves and scrolls per 10 seconds. Never which keys
  • Focus, sleep, mic and cameraWhich Focus is on; when the Mac slept; whether mic or camera are in use. No sound or image
  • NotificationsThe unread badge count per Dock icon. Never the contents
  • Network and powerA network fingerprint, the Wi-Fi name, battery or mains, connected headphones

Off until you turn it on

  • MailSender, recipients and subject. Never a body privacy.mail
  • MessagesSender, chat name and time. Never the text privacy.messages
  • Screen textText read off the focused window by on-device OCR ocr.enabled
  • Screen factsUp to three short facts about the screen, from a vision model in your local Ollama ocr.vision.enabled
  • Page textThe visible text of the front browser tab browser.pageText
  • HearingTranscripts of speech near the Mac and of the far side of a call, by a local Whisper server, while you press Listen (or, with audio.autoMeetings, during meetings) audio.enabled
  • ClipboardOnly the kind (link, code, text, file) and size of what you copied clipboardEnabled
  • Obsidian vaultPaths of notes that changed in the one vault you name vault
  • Devices nearbyA hashed id per device on a network you consented to experiments.presence

Not recorded at all: which keys you press, notification contents, clipboard contents, URL query strings, mail bodies, Messages text, sound. Every event is cleaned once before it is written — secrets, e-mail addresses, phone and card numbers, your user name in paths — and everything downstream reads the cleaned value.

Can leave

Nothing, until you configure it. Then only:

  • Sanitized text from the record, plus what you type in the chat and images you attachto The model endpoint you chose. Point it at 127.0.0.1 and no text leaves your MacWhen Gnomon answers or writesPoint at or tap a row on the left to see what the model gets from it.
8 more, each behind a setting you have not set
  • The embedding model’s weights — a download, no text is sentto Hugging FaceOnce, the first time embeddings run
  • A notice’s title and text, and titles of finished workto The ntfy URL you setOnly if notifications.ntfy is set
  • A gh pr view request, with your own loginto GitHubOnly if gh is installed and signed in
  • Web pages Gnomon fetchesto The siteWhen you ask Gnomon to read the web
  • Internal scoring questionsto api.typesafe.aiOnly if TYPESAFE_API_KEY is set
  • Tool calls to your own servicesto The serviceOnly for services you list under integrations
  • A background job’s prompt, and what Claude reads from the recordto Anthropic, through your own Claude Code loginOnly if hands.claude is set
  • Whatever an MCP client readsto That client’s own model providerOnly if you connect Claude Code or another agent

The model sees cleaned fields only: app, project, window titles, shell commands, branch, meeting title and attendee count — and page text, mail subjects, screen facts or heard speech only when you turned those sensors on. Every call is listed in the Ledger, with its cost. The full privacy page.

How an observation travels

One direction, one pass each. Point at or tap a stage.

  1. 1Sensorswindow, git, shell, calendar, agent
  2. 2Cleaned oncesecrets, addresses, paths
  3. 3The logappend-only, SQLite, yours
  4. 4The foldrules, in order, one state
  5. 5Effectsmemory, embeddings, the model
  6. 6AnswersToday, the board, chat, MCP

An observation moves left to right and never back. The model sits at stage five, behind one audited door, and sees only cleaned values.

The architecture, in full · Why it is built this way

One Thursday morning

A made-up week. The morning card knows what you did yesterday and where you left off. It lists what you still owe before a client demo, writes a research brief with sources, tests a rule on your record before you keep it, and takes a typed correction as your fact. Every model call lands in the Ledger.

Nothing in it is real data. The demo is this same week, in your browser.

Ask it from Claude Code

The same week, asked from outside. Claude Code, with only Sundial’s read-only MCP tools, tells the story of the week and what is still owed — then opens the release call it mentioned, down to the raw capture.

claude mcp add sundial --scope user -e SUNDIAL_HOME="$HOME/.sundial" -- node "$PWD/packages/mcp/bin/sundial-mcp.js"

Install in a minute

git clone https://github.com/Angelista-Enterprise/sundial.git && cd sundial
node bin/sundial install
node bin/sundial open

install checks your Mac, builds everything, writes ~/.sundial/ and starts Sundial at login. open signs your browser in and walks you through the macOS permissions. The first observations arrive within a minute.

Gnomon needs a model to talk. Without one, Sundial still records and the Today screen still shows your day. Pick one on the setup page, or two lines in ~/.sundial/.env:

# local, nothing leaves your Mac (Ollama)
SUNDIAL_LLM_BASE_URL=http://127.0.0.1:11434/v1
SUNDIAL_LLM_MODEL=qwen3:8b

Any OpenAI-compatible endpoint works. macOS only, for now: the sensors are native Swift helpers. Getting started · Models · Permissions