cdb
chip database — sign in to continue
✓ Signed in as
Waiting for an admin to approve your account. This
page unlocks automatically once you're approved.
log out
privacy policy · terms of service
users
People sign in with Google. A first sign-in waits here
for approval — approve it as a new account (you can change the username,
which is what their entries are recorded under), or link it to an
existing account. A user can change the database, a read-only user can
only look (and their tokens are read-only too); only admins manage
users. Disabling ends their sessions and their agents' tokens at
once.
loading…
close
new group
A group draws a named outline around these nodes on the
graph. Click its name to open its notes and members.
name
create group
cancel
locations & tools
Location and tool values are picked from this one shared
list. Anyone who can edit the database can add or remove a name;
removing one leaves the entries that already use it as they are.
add
loading…
close
move
new location
move
cancel
requests & bug reports
Post a feature request or bug. Whoever posted an item, or an
admin, clears it once it has been handled.
loading…
feature request
bug report
submit
close
filter
✕
Only entries matching every part of the filter
are drawn, searched, and listed for review. Each node, process and
measurement is judged by its own project, recorder and date.
from date
any date
nodes by the day they were created, processes and
measurements by the day they were done
show everything
fit
re-layout
filter
groups
collapse all
hide dead branches
?
boxes show each node's in-place steps (spin→jdep→sem…) · click a box for its timeline · scroll = zoom · drag = pan/rearrange · click a search result to zoom to it
✕
restore from history
every change is a git commit — pick the one to restore the
database to. Nothing is lost: the restore is itself a new commit, so the
current state stays in history and can be restored the same way.
cancel
github backup
loading…
back up now
close
API tokens
Agents and scripts can't sign in with Google, so give each
one its own token. It acts under its own name (that is who its entries
are recorded as), with user rights, and stops working when it expires,
when you delete it, or the moment you are disabled. A read-only token
can look but never change anything. What your agents record is yours to
confirm. The token is shown once.
loading…
expires in
1 hour
8 hours
1 day
7 days
30 days
90 days
your account is read-only, so its tokens are too
create token
Token for copy it now, it won't be shown again :
copy
close
google drive mirror
loading…
sync now
close
agent skill file & API
cdb has no built-in speech-to-text or LLM. Bring your own — whisper,
Claude, any LLM, or a plain script — and connect it over the HTTP API.
Anything an agent records arrives unconfirmed (in review ),
or as a proposal waiting in pending .
Give the agent its own token: ⋯ → API tokens (or on the
server, cdb user token <agent-name> --owner <you>).
Give the agent the skill file — it explains every call:
For Claude Code:
Set CDB_URL and CDB_TOKEN in the
agent's environment, and tell it which project to create entries in.
Reference: /api/openapi.json (every
endpoint, for signed-in users and tokens) · operations as LLM tool definitions:
/api/v1/ops?format=anthropic or ?format=openai
close