nano-zyrkel
an open-source project by schlein-lab · part of Zyrkel

Tiny programs
that work for you,
every hour, every day.

Drop one into a GitHub repository and it runs by itself — watching a website, tracking a dataset, building you a dashboard. No server to rent, no hosting bill, nothing to keep alive. GitHub does the work in the background; you read the results when you wake up.

View on GitHub See one running
Rust core WASM browser kit Runs on Actions cron MIT-licensed

Three things a nano-zyrkel does

Each instance is a small, config-driven agent specialised on one job.

Watch

Monitor pages, feeds, datasets, or price points. Ping you only when something meaningful changes.

Collect

Aggregate many sources into one digest. Filter by your rules. Wake up to a clean morning brief.

Work

Run a job: render a dashboard, process a manifest, ship a tracker. Every commit is the audit trail.

How it works

Two cores. One repo per agent. Cron does the rest.

01

Pick a scaffold

Choose what kind of agent you want — data-pipeline, interactive-app, or showcase — and start from a ready-made template.

02

Push to GitHub

Enable Actions. Your repo now contains the binary core, the WASM core, the CI workflows, and a hats/config.json describing the agent.

03

The cron takes over

Every tick: fetch → check → notify → act. Results commit to staging/. Pages serves the dashboard. You read the diff to audit.

04

Upgrade by merging a PR

The bundled update-core.yml workflow opens a PR every week with the next compatible release. Merge it. That's the upgrade.

nano-zyrkel architecture The SDK ships a Rust binary core and a WASM browser core. Your own repository pulls one or both, defines a schedule and config, and produces results into staging/ and a Pages site under docs/. schlein-lab/nano-zyrkel — the SDK (versioned) core Rust binary that fetches, checks conditions, notifies bin-vX.Y.Z wasm-core Browser kit: charts, filters, dashboards wasm-vX.Y.Z pull pull your repo — one repo = one agent .github/workflows/cron.yml — when it runs hats/config.json — what it does staging/ — where results land docs/ — what GitHub Pages serves every commit ⟶ the audit trail · cron runs the loop · you only read the diff

See one running before you install anything

Three reference nano-zyrkels. Every commit to the SDK has to keep them green.

pipeline · runs minimap2 in your browser

CrowdGenome

Distributed dark-genome mapping. minimap2 compiled to WebAssembly — your browser does the alignment, no upload required.
tracker · theme-clinical

VUS Tracker

Variant intelligence platform. 4.4M ClinVar entries, refreshed daily.
interactive-app · theme-magazine

Helix

Interactive human-genetics teaching suite. Pure WASM, zero backend.
showcase · cinematic

Showcase room

Cinematic portal listing every published nano-zyrkel.

More from the catalogue

template · maildesk-codex-telegram

Mailbox auto-responder

Polls your inbox every 30 minutes, drafts a reply with an LLM, sends a Telegram preview, only delivers after /approve. SMTP + IMAP, no server.
live · nano-zyrkel-incoming

Public ingress channel

A static form that turns visitor messages into GitHub Issues, processed by a Rust binary on a 30-minute cron, forwarded to Telegram. No client-side secrets.

The bigger picture

nano-zyrkel is the open-source SDK arm of a larger ecosystem.

Zyrkel

zyrkel.com

The desktop product nano-zyrkel descends from. Docks into your apps, learns your routines by watching once, then quietly takes them over.

Visit zyrkel.com →

schlein-lab

schlein-lab.com · github.com/schlein-lab

The lab behind nano-zyrkel and its reference agents. Where research meets reusable infrastructure — every published agent ships its source.

Visit schlein-lab.com →

Build a tiny agent. Let it work while you sleep.

View on GitHub Read the docs