AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
A private memory index shared by all your AI agents. Open source, self-hosted, with Korean-first search. Coming soon.
Developer toolsPython · JavaScriptGitHub @junwonkim07OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
One tidy, private memory for all your AI agents across your devices
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
One tidy, private memory that every AI agent you use can read — on every device you own.
Claude Code · Codex · Aside · claude.ai (web & iOS) — same notes, same search, one small server.
Every agent keeps its own little memory. Claude Code remembers per folder, Aside has its own notes, the phone app knows nothing about your laptop. tidy-one gives them one place to look:Read the full README ↗Every agent keeps its own little memory. Claude Code remembers per folder, Aside has its own notes, the phone app knows nothing about your laptop. tidy-one gives them one place to look:
flowchart LR
subgraph Devices
mac["MacBook<br/>Claude Code · Codex · Aside"]
win["Windows laptop<br/>Claude Code · Codex"]
ios["iPhone<br/>Claude app"]
end
repo[("claude-memory<br/>private git repo<br/>(markdown)")]
subgraph VPS["tidy-one server (Vultr, Seoul)"]
sync["memory-sync<br/>every 2 min"]
bm["Basic Memory MCP<br/>127.0.0.1:8000"]
proxy["mcp-auth-proxy<br/>OAuth + auto TLS"]
upd["tidy-one-update<br/>every 3 min"]
end
gh[("tidy-one<br/>this repo")]
mac <-- "SessionStart pull / Stop push" --> repo
win <-- "SessionStart pull / Stop push" --> repo
repo <--> sync --> bm
proxy --> bm
ios -- "custom connector (HTTPS)" --> proxy
mac -. "local MCP (stdio)" .-> mac
gh -- "git pull + deploy.sh" --> upd
| Piece | What it does |
|---|---|
claude-memory repo | Markdown memories with frontmatter. Claude Code's autoMemoryDirectory points at it on every device. |
| Basic Memory | Indexes the repo (SQLite FTS + sqlite-vec, paraphrase-multilingual-MiniLM-L12-v2) and serves MCP tools like search_notes. Configured never to rewrite your files. |
memory-sync | Keeps the server's copy in step with GitHub, and pushes edits made through the server. |
mcp-auth-proxy | Public HTTPS + OAuth login in front of Basic Memory, so claude.ai can connect. Off until you turn it on. |
tidy-one-update | Pull-based auto-deploy of this repo. |
scp server/bootstrap.sh root@<server-ip>:
ssh root@<server-ip> sh bootstrap.sh
bootstrap.sh installs git, uv, Basic Memory, a firewall (22/80/443) and swap, creates a memory user, and prints two deploy keys. Add them on GitHub (memory repo: read-write, this repo: read-only), run it again, and it clones both repos and deploys.
git clone [email protected]:<you>/claude-memory.git ~/claude-memory
Merge client/macos/claude-settings.example.json into ~/.claude/settings.json, then register the local MCP server:
uv tool install basic-memory
bm project add claude-memory ~/claude-memory --default
sh server/enable-connector.sh <server-ip>
This creates a password on your Mac only, sends its bcrypt hash to the server and starts the HTTPS connector at https://<ip-with-dashes>.sslip.io/mcp. Add that URL in claude.ai → Settings → Connectors.
Push to main. Within ~3 minutes the server's tidy-one-update.timer notices, resets /opt/tidy-one to origin/main and runs server/deploy.sh, which only restarts what changed.
ssh root@<server-ip> /opt/tidy-one/server/update.sh --force # deploy right now
ssh root@<server-ip> journalctl -u tidy-one-update -n 20 # what happened
server/
bootstrap.sh one-time VPS setup
deploy.sh idempotent deploy (units, Basic Memory config, restarts)
update.sh pull-based auto-deploy, run by tidy-one-update.timer
enable-connector.sh owner-only: turn on the public connector
bin/memory-sync.sh git pull/commit/push for the memory repo
systemd/ basic-memory, memory-sync, memory-proxy, tidy-one-update
client/macos/ settings example, Aside memory mirror
docs/research/ design research (Korean): architecture, engines, devices, OSS survey
Based on the design research:
/etc/tidy-one/proxy.env (root-only).127.0.0.1 only. The proxy is the single public entry point and is off by default.