Skip to content

Davincc77/klickdskill

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

209 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

.klickd — One file. Any model. No server.

When it all .klickd

.klickd version License: CC0 DOI

Official page for the open .klickd format → klickd.app/klickdskill


Your AI forgets you. Every. Single. Session.

You explain your level. Your goals. Your context. Then the session ends — and tomorrow, you start from zero again. Every time. With every model.

.klickd fixes that. One encrypted file on your device. Drop it into any AI. It picks up exactly where you left off — whether that was GPT-4o yesterday, Claude this morning, or Llama tonight.

No account. No server. No one else holds your memory.


What it looks like

{
  "klickd_version": "3.5.1",
  "created_at": "2026-05-21T00:00:00Z",
  "encrypted": false,
  "domain": "education",
  "user_preferences": "You are continuing a session with a learner working on calculus. Resume as if you have been here from the start."
}

Save as profile.klickd. Load it in any compatible client. Your AI knows who you are.

That's it.


Why not just use Mem0, Letta, or OpenMemory?

They all require a running server, a Docker container, or an API key. Your memory lives in their infrastructure — not in your hands.

.klickd is a file. It lives on your device. It travels with you. It works offline. And it's encrypted client-side with AES-256-GCM + Argon2id — the server never sees your context.

.klickd Mem0 / OpenMemory PAM Letta agentmemory
Zero server process ❌ Docker + Qdrant ❌ SDK + transport ❌ runtime ❌ Node port 3113
Client-side encryption ✅ AES-256-GCM + Argon2id ❌ server-side
No API key required
Portable file (drag-and-drop)
Pedagogical schema ✅ curriculum, mastery, CEFR
DOI-referenced benchmark
GDPR / Luxembourg jurisdiction

The numbers

Benchmarked across 23 subjects, 115 profiles. Scorer: qwen/qwen3-32b via Groq.
Full methodology: DOI 10.5281/zenodo.20320480

Sequence What was tested Δ WITH vs WITHOUT
Seq 1 — 115 profiles Core pedagogy +13.9 pts avg (min +12.8, max +19.2)
Seq 2 — §31 recovery Migration continuity +9.5 pts (with recovery phrase)
Seq 3 — Soul Handoff Cross-model identity +14.0 pts (IC ±7.2)

Try it now

  • Playground — load a .klickd file live, see what the AI receives
  • klickdskill docs — full specification and integration guides

Install

Python

pip install klickd

Node.js / TypeScript

npm install @klickd/core

Examples

File Who it's for
examples/student_fr.klickd French high-school student, maths, Socratic mode
examples/professional_en.klickd Mid-level developer upskilling into ML
examples/family_plan.klickd Child profile with ADHD support and shared family context
examples/minimal.klickd Cold start — 5 fields only, valid v3.5
examples/full_v34.klickd Full reference file — all fields populated

Integrations

Provider Guide
OpenAI (GPT-4o, o1, …) docs/integrations/openai.md
Anthropic (Claude Opus, Sonnet, …) docs/integrations/anthropic.md
Groq (Llama, Qwen, …) docs/integrations/groq.md
OpenRouter (multi-provider Soul Handoff) docs/integrations/openrouter.md
Any provider (generic pattern) docs/integrations/generic.md

Experimental POC: integrations/hermes/ — Hermes Agent as workflow runner, .klickd as portable state layer. Local dry-run only; not a production integration.


Schema validation

pip install jsonschema
python -c "
import json, jsonschema
schema = json.load(open('schema/klickd-v3.4.schema.json'))
doc    = json.load(open('examples/student_fr.klickd'))
jsonschema.validate(doc, schema)
print('Valid.')
"

Schema: schema/klickd-v3.4.schema.json


Prior art

To our knowledge, no existing format combines zero-process portability, client-side AES-256-GCM + Argon2id encryption, a structured pedagogical schema, and a DOI-referenced reproducible benchmark.

Evaluated against: Mem0, PAM (arXiv:2605.11032), Letta/MemGPT, Cortex, Opal (arXiv:2604.02522), MeMo (arXiv:2605.15156), agentmemory (~15K stars).
Full analysis: Zenodo preprint


Long context vs portable state

.klickd is not a replacement for long-context models or context-window extension — and it is not in competition with the GPU / runtime infrastructure that makes those windows possible. The two address different layers of the same problem:

  • Longer context helps the model fit more. GPU and runtime infrastructure (extended windows, KV-cache offload, streaming attention) expand what a single inference call can process.
  • Portable state helps the system repeat less. .klickd reduces what the model has to repeatedly process across sessions, vendors, and models, by carrying user-level state as a portable file.

They are complementary. A larger window does not, on its own, retain who the user is between yesterday's GPT-4o session and tomorrow's Claude session — that is a state-persistence concern, not a capacity concern. Equally, a .klickd payload does not stretch a single call's working memory.

For most real workloads the useful question is not "long context or portable state" but "long context and portable state": expand capacity at the runtime layer, and trim repetition at the state layer. RFC-003 (Context Cost Benchmark) is being designed to measure exactly this — see §9.1 of the RFC for the non-normative framing.

Insight prompted by a DEV.to discussion with VoltageGPU — see ACKNOWLEDGEMENTS.md.


Cite

@misc{klickd2026,
  title  = {.klickd — Open Learner Context Format, v3.5},
  author = {Cirilli, Vincenzo},
  year   = {2026},
  doi    = {10.5281/zenodo.20320480},
  url    = {https://doi.org/10.5281/zenodo.20320480}
}

Badge

[![.klickd compatible](https://img.shields.io/badge/.klickd-v3.5%20compatible-0066CC?style=flat-square&logo=json)](https://github.com/Davincc77/klickdskill)

Full Specification

SPEC.md — encryption (AES-256-GCM), all field references, teaching modes, Soul Handoff, JSON Injection Guard, benchmark namespace, memory decay, shared context, versioning policy.

Looking ahead — .klickd v4 preview (non-normative, not GA)

The current and recommended production format is v3.5.1. In parallel, the repository hosts a preview track for the next iteration of the same .klickd standard family:

The preview targets v4.0.0-preview.1. No SDK release, no npm / PyPI / Zenodo publication, and no git tag are associated with it. v3.x readers MUST ignore preview fields; v4-preview readers MUST preserve unknown fields verbatim.


License

CC0 1.0 Universal — Public Domain. No permission required. No vendor lock-in.


Made in Luxembourg · GDPR-native · klickd.app