Alexeyprompts

Read the blog: https://clickhouse.com/blog/agentic-coding

Alexey Prompts

A viewer of Claude Code sessions with ClickHouse backend.

How to use

Create the database and tables. The raw table uses JSON type hints plus a few
materialized columns and a text index so the UI's queries stay fast (see
schema.sql for the full definition and the reasoning):

Upload your sessions:

This is likely optional:

Uploading only new data (incremental updates)

After the first upload, you don't need to re-send everything. Re-running the
commands above is always *safe* (the raw table is a ReplacingMergeTree, so
duplicates collapse), but it re-reads and re-sends every session each time.

Use upload_incremental.sh to upload only new sessions and new entries
appended to existing sessions:

On each run it uploads the union of two sets:

1. Sessions ClickHouse doesn't have yet — it asks the raw table which
   paths are already loaded and uploads any local .jsonl that's missing.
   This does *not* rely on file mtimes, so it works when you collect from
   several machines, at different times: copy the .jsonl files over (rsync,
   scp, …) and upload later. (Plain mtime checks miss these, because copying
   preserves the original, older mtime.)
2. Sessions that grew — files modified since the previous successful run *on
   this machine* (tracked by the marker file ~/.claude/.ch_last_upload) are
   re-uploaded so appended entries get in.

Any overlap is deduplicated by the table's ORDER BY (sessionId, timestamp,
uuid), so nothing is duplicated. It's idempotent, so it's a good fit for cron,
e.g. hourly:

Options (environment variables):

- CH_SECURE=1 / CH_SECURE=0 — force TLS on/off (defaults to on for any
  non-localhost host, which ClickHouse Cloud requires).
- PROJECTS=/path/to/projects —…