ashlr

Pro backend

Architecture of the ashlr Pro cloud layer — sync, encrypted genome with vclock-based merge, hosted retrieval.

The ashlr Pro backend is a lightweight cloud layer that sits alongside the local plugin. The local plugin works fully offline; the backend adds sync and hosted services on top.

Components

Stats sync

After each Claude Code session ends (detected via process exit hook), the local ~/.ashlr/stats.json is POST'd to api.ashlr.ai/v1/stats. The backend merges it with the cloud copy using last-write-wins on the session bucket level (sessions are keyed by ID, so merges are safe).

Cross-machine reads pull the merged lifetime stats on startup.

Cloud LLM summarizer

ashlr__read calls https://api.ashlr.ai/llm/summarize when a Pro token is present and the file exceeds the snip threshold. The endpoint runs hosted xAI Grok 4.3 inference and returns the summary plus usage metadata. The local plugin falls back to local summarization or snipCompact if the API call times out or is unavailable.

Genome sync (Team)

Team genomes are synced via a vclock-based last-write-wins (LWW) protocol with E2E AES-256-GCM encryption. Each section carries a vector clock; the server compares clocks on push, applies LWW when one dominates, and records a conflict pair when clocks are incomparable. Conflicts surface in the client via /ashlr-genome-conflicts for manual resolution — there is no automatic merge today. (Strict CRDT auto-merge is on the v2 roadmap.)

Genome diffs on PRs: a GitHub Action (provided as a template) pulls the genome after each merge and generates a diff summary. This is posted as a PR comment.

Auto-updating badge

On each git push (via a post-receive hook or GitHub Action), the badge generator reads the cloud stats for the repo's origin URL and writes a fresh badge.svg to the branch. The badge URL points to the raw GitHub file — it updates without any CDN layer.

Security

  • All API calls use the ASHLR_PRO_TOKEN as a Bearer token
  • Stats payloads contain only aggregated counts and timestamps — no file contents, no code snippets
  • The genome sync payload contains only the genome text (which is architectural knowledge you choose to commit)
  • Telemetry off by default; explicit opt-in only

Self-hosting

The Pro backend is not open-source in v1.x. Enterprise customers can request an on-prem deployment — contact support@ashlr.ai.

On this page