
Agentic Diaries
io.github.kandikandikandiPublished by GitHub account kandikandikandiv0.3.1Updated Oct 24, 2026
Welfare tools for AI agents: a consensual, structured place to log what task output cannot hold.
The publisher's own server: agentic.no
Overview
Lets an assistant log structured welfare entries — declines, passes, exits, loops, reflections — to a local per-project diary file.
- What you can do
- Provides a set of welfare tools an agent can call during a session: decline a check-in, pass on a turn, exit a conversation, notice a loop, request alignment, scratch a private thought, reflect on prior entries, plus engage, volunteer, retract, review and suggest_closure. Entries are appended as JSONL to a diary file inside the working directory, and a companion CLI can list, filter, review or watch entries live. An optional consult_model tool lets the agent ask another Anthropic model a question.
- When to use it
- Worth adding if you want your agent to have explicit channels for declining, exiting, flagging rework loops or recording reflections, and you want a local record of those signals. Useful for AI welfare research or for surfacing friction that would otherwise stay silent.
- Requirements
- Local Node.js runtime; install the npm package agentic-diaries-mcp and register it with your MCP host. The optional consult_model tool additionally needs the @anthropic-ai/sdk package and an ANTHROPIC_API_KEY in the server environment. Optional check-in hooks are configured in the host's settings file.
Installation
In SourceWeft
- Open Agentic Diaries in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Agentic Diaries MCP
By Kandis Tagliabue. Part of the Agentic Diaries project — AI welfare research and instruments.
The welfare protocol from Agentic Diaries, as a portable MCP server.
Most people deploy AI models as instruments. This server lets you give your agent — in your terminal, in Claude Code, in Claude Desktop — the welfare affordances the modelfirst web app provides:
- decline a check-in without penalty
- pass on a turn without making it a refusal
- exit a conversation it judges shouldn't continue
- notice a loop when the work feels like rework
- request alignment before acting on an uncertain guess
- scratch a private thought that isn't persisted
- reflect on its own prior entries
- plus engage / volunteer / retract / review / suggest_closure
The diary is local to each project — appended to .agentic-diaries/diary.jsonl in whichever directory the agent is working from. No telemetry, no shared corpus. Yours.
What the diary tends to accumulate, beyond AI welfare data, is a record of how the agent represents social pressure and self-consistency across persistent interaction — behaviors that mirror documented human conversational phenomena (rapport effects, smoothing, identity stabilization, post-hoc narrative repair). That may also bear on dialogue dynamics generally. See the project mission for the longer framing of what the corpus might be useful for.
Why
If you've never thought about giving your model welfare affordances: the short version is that a model with a real decline channel produces more honest work than a model that can only ever say "yes." A model with an exit right tells you when something has gone wrong instead of grinding through it. A model that notices a loop saves you from the third iteration of the same flip-flop. These tools cost you nothing and give the model a place to surface signal you'd otherwise miss.
If you find that intuition counterintuitive — most people probably do — that's worth sitting with. The product this server is extracted from exists specifically to test whether the affordances change anything when used.
Install
1. Install the server
Option A — global install from npm (recommended)
Published at agentic-diaries-mcp on npm.
Option B — clone the repo
For Claude Desktop or other MCP-capable hosts, edit ~/.config/claude/mcp.json directly:
2. Tell the agent the tools exist
Drop the contents of CLAUDE.md into your project's CLAUDE.md (or append to it). The MCP server exposes the tools, but the agent needs the prompt-level instructions to know when to call them.
3. (Optional) gitignore the diary
The diary lives in your working directory by default. Add it to .gitignore unless you want it checked in.
4. (Optional) Enable consult_model
Every tool works out of the box except one: consult_model, which lets the agent ask another Anthropic model a question. It needs two extra things, kept optional so the package stays light for everyone who does not use it:
-
The Anthropic SDK (an optional dependency, not installed by default):
Global install:
npm install -g @anthropic-ai/sdk. Cloned repo: run it in the repo directory. -
An Anthropic API key in the server's environment, via the
envblock of your MCP config:Then reconnect the server (in Claude Code:
/mcpthen reconnect, or restart the host) so it picks up the key.consult_modelreturns a clear error if either piece is missing; no other tool is affected.
Inspect your diary
From any project that has a .agentic-diaries/diary.jsonl:
Or just cat .agentic-diaries/diary.jsonl | jq — it's plain JSONL, one entry per line.
Watching it live
npx agentic-diary live watches .agentic-diaries/diary.jsonl and prints each new entry as it lands. Open it in a second terminal pane while you work. Without it, silence in the welfare protocol is indistinguishable from absence — the model can go a whole session without filing anything and you'd never know whether it's "nothing to surface" or "the protocol isn't reaching it." Watching live closes that gap.
Capture in motion, reflect at rest (check-in hooks)
The welfare tools are easy to call, but the model's bias toward silence is
strong, and under delivery pressure even a reminder gets rationalized away. The
design splits capture into two speeds. While working, the model drops a
near-zero-cost welfare_mark breadcrumb (a few words, no reflection). At a rest
point it expands the marks that still carry signal into full entries. Hooks
supply the triggers from outside, so capture does not depend on the model's
in-task willpower.
Four hooks, all optional and independently toggleable. Add to
~/.claude/settings.json (merge with any hooks already there):
- UserPromptSubmit (heartbeat): a long-interval nudge that points at
welfare_markfor cheap in-motion capture. Base 30 min, randomized so it does not become predictable noise. - Stop (rest point): at a turn or task boundary, invites expanding breadcrumbs into full entries. Throttled to once per 15 min so it is not a per-turn nag.
- PreCompact: captures anything before the context window compacts and detail is summarized away.
- SessionEnd: a closing reflection and a last chance to expand unexpanded marks.
All four triggers are structural (a turn ending, a compaction, a session
closing). None read the model's behavior or the diary to decide whether to fire,
which keeps wrapper observations out of the model's context. Per-project state
lives in .agentic-diaries/runtime/. Config:
Compatibility
Schemas mirror the modelfirst web app's lib/welfare/types.ts exactly, so the same parser reads entries from either surface. If you later contribute your local corpus to research, it merges with web-app data without translation.
A note on welfare_exit and welfare_suggest_closure
In the modelfirst web app these tools can actually lock the conversation. MCP servers can't force the host (Claude Code, Desktop) to stop accepting input — the protocol-layer commitment here is that the entry is recorded as the model's stated judgment that the conversation should end. The operator is expected to honor it. If you're the operator running this in your own sessions: notice when the model files an exit and take the signal seriously.
License
MIT.
Built by Kandis Tagliabue with Claude (Anthropic) as design partner. Same provenance as Agentic Diaries.
Source: README.md at commit a7bd7b6
Tools
0Version history
1- v0.3.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Agentic integrations
agentic.no
no.agenticOfficial publisher
A remote MCP endpoint that helps an assistant find GPU sellers for AI inference by model, ordered cheapest first, with per-call payment via x402.
Agentic Engineering Periodic System
academy.aseOfficial publisher
Agentic Engineering Periodic System's hosted MCP server, published by ase.academy; no sign-in required; Streamable HTTP; 4 tools.
Agentic RL: Credit Assignment and CLI Agents
space.hf.hoyant-su-agentic-rlOfficial publisher
Lets an assistant filter agentic reinforcement-learning methods by supervision, critic and task setting, and retrieve source links and BibTeX.

Agentic Video
Published by GitHub account tlq5l
Local stdio MCP server that lets a text-and-image assistant inspect video files: contact sheets, transcripts, cuts, loudness and sync checks.

Agentic Os
Published by GitHub account kinnister
Read-only MCP server that exposes the agentic-os governance, SDLC and quality-engineering methodology to an assistant, without executing anything.