dint

One local chat API. Engine CLIs do the work. Codicent Logbook is the ledger.

Site: izaxon.github.io/dint

Router.start_chat / send / cancel
        │
        ├─ Engine          Claude / Codex / Grok / Copilot CLI  (resume via session id)
        └─ Logbook         post_message / get_messages / get_history
              │
              └─ ChatLog   #user vs #bot, parentId chain, GetMessageHistory

Coding agents already ship as official CLIs. Each one keeps its own sessions, transcripts, and resume ids. dint does not reimplement them. It starts a chat, streams a turn, and writes every message to Logbook as an append-only thread. A job is just a tagged Logbook message (#job); dint serve runs it.

v0: local, four engines, webhook jobs. Not a hosted product and not a desktop UI.

Install

Python 3.11+ and pipx, at least one engine CLI on PATH (grok, claude, codex, or copilot), and logbook-server on PATH.

# Windows
iwr https://logbook.codicent.ai/install.ps1 | iex
# Linux / macOS
curl -fsSL https://logbook.codicent.ai/install.sh | bash

pipx install dint-cli

The PyPI name is dint-cli (dint is taken). From a checkout: pipx install . or pip install -e ".[dev]".

Then, in any folder:

dint

That starts logbook-server and a background dint serve if they are not running, then opens a chat in the current directory (same idea as running grok in a new folder). Config lives in ~/.dint. dint grok "Summarize this repo" is a one-shot; dint status checks Logbook, serve, and engine CLIs.

Chat

dint
dint grok "Summarize this repo"
dint start grok .
dint send <chat_id> "Summarize this repo"
dint chats
dint list <chat_id>
dint show <chat_id>

Bare dint resumes the latest chat for this folder, or starts one with the first engine CLI on PATH (DINT_ENGINE to pick). /new starts a fresh chat; /quit exits. Logbook and dint serve keep running in the background.

Python:

from dint import Router

r = Router()
chat_id = r.start_chat("claude", cwd=".")
for ev in r.send(chat_id, "Summarize this repo"):
    print(ev.type, ev.text)

Jobs

dint and dint job start a background dint serve if it is not running. Enqueue from the CLI or by posting a #job in Logbook. Run dint serve in the foreground if you want the webhook logs.

dint serve
dint job grok "What can you do?"
# job    <logbook-id>
# chat   <chat_id>
dint list <chat_id>

From Logbook:

@test #job #claude
{"engine":"claude","cwd":"/src/myproj","prompt":"Summarize this repo"}

or @test #job #grok Summarize this repo.

dint serve listens on http://127.0.0.1:8787/webhook. If register fails, start logbook-server with LOGBOOK_WEBHOOK_URL=http://127.0.0.1:8787/webhook. Completed turns are stored on #chat-<id> like a normal send. Ack is #job-run (not #job, so it does not loop).

Agents should use Logbook MCP (post_message / get_messages) rather than a dint MCP. The contract is in .grok/skills/dint-jobs/SKILL.md.

Ledger

Each chat is a Codicent-style thread: the header is the root; every later message sets parentId to the previous one. User turns are tagged #user, engine replies #bot. dint list reads #chat-<id> (full body) and merges GetMessageHistory for the parent chain — history alone can truncate long bot JSON.

License

MIT. See LICENSE.