Open-source local-first engagement
Build retention flows without the infra maze
Source-first, config-driven mobile engagement logic that runs on-device. Ship quickly with clear ownership.
Built for
Indie Builders
Launch onboarding nudges, streak reminders, and re-engagement flows in one sprint.
Product Teams
Run retention experiments before committing to a full engagement platform.
Agencies
Reuse a proven engagement foundation across client apps with predictable handoff.
Agent-First Builders
Let your AI agent read, modify, and extend engagement rules safely.
Get started
Quickstart
Install OpenClix skills, then iterate with config-driven engagement logic you fully own.
npx skills add openclix/openclix
Vendor source into your repo
Bring OpenClix client code in-repo as checked-in source so you can inspect and own every integration detail.Connect config JSON + event hooks
Wire app-resource or HTTPS JSON config with app events so rules react without backend plumbing.Trigger rules and ship local engagement flows
Run local notifications and in-app messaging logic on-device with debuggable reasons and safe edit points.
Foundation
Core Pillars
OSS
- MIT/permissive mindset
- transparent logic
- forkable and auditable
No Friction / No Dependencies
- no backend required
- no hosted control plane required
- no auth/API key for local-first use
- vendored source, not package runtime dependency
- no proprietary SDK lock-in
AI AGENT FRIENDLY
- legible folder structure
- explicit interfaces and schemas
- examples, fixtures, and clear edit points
- agent-oriented docs/prompts
Belief / Mission
Retention tooling should be simple, open, and fully yours.
OpenClix gives builders 100% control with source in-repo, no complex setup burden, and a single-file configuration model.
It is intentionally agent-friendly, with explicit interfaces and clear edit points for safe, reviewable iteration.
Common questions
FAQ
Quick answers before you adopt OpenClix.