कामदेव

kama.dev

A small studio that builds and runs its own software.

We ship to the edge and to small machines. Everything below is something we actually made and still operate — never a mockup, never a slide.

aśoka

Shipped

Things that are out, and still running.

Hermes Session Ref

Hermes Desktop plugin · MIT

Reference another session by name in the Hermes Desktop composer — no copying session IDs, and nothing injected into context.

You type @session in the composer and pick from live session suggestions. Picking one inserts a compact @session:"<title>" reference into your draft.

The reference is not expanded and no session context is copied. Hermes resolves it with its own session search, so it knows exactly which session you mean and your context window stays clean. That restraint is the whole design.

Works in: Hermes Desktop (the app loads the plugin; the CLI and gateway alone do not)
Requires: Hermes 0.21 or newer
Registers: a composer.atCompletions source with the Desktop plugin SDK

Install

hermes plugins install session-ref
hermes plugins enable session-ref

desktopplugincommunity tier

Repository

The list grows as things ship. It does not get padded: if it is not finished and running, it is not here.

cūta · mango blossom

In the Hermes catalogue

Reviewed by Nous Research and merged upstream.

Nous Research maintain a human-reviewed plugin catalogue for Hermes Agent. Every entry is pinned to an exact commit, and each one has to declare its capabilities before it is accepted. Ours went through that review and was merged into the repository itself.

Catalogue entry

name: session-ref
repo: kama-dev/hermes-session-ref
maintainer: kama-dev
tier: community
category: desktop
version: 0.1.0
requires_hermes: >=0.21.0
sha: 9b6f03fb0ccd9113e2211fb7dd01df88ad45a8ba

The receipt

ecd560cplugin-catalog: add session-ref (community, desktop)NousResearch/hermes-agent

The catalogue is a set of YAML files in the Hermes repository — one per plugin, each pinned to a full 40-character commit SHA.
The entry is checked by CI on every change: the pipeline clones the plugin at its pinned commit and runs hermes plugins validate against it.

navamālikā · jasmine

What we build

We take work we can finish ourselves. If a job needs a team, we turn it down.

Services

Python services behind systemd, on small machines. SQLite or Postgres, whichever the job actually needs. Resource-capped per project so one thing cannot take another down.

Web

Cloudflare Pages, Workers, Functions and DNS. Static pipelines that build one self-contained page per route. Caddy with automatic TLS where a real origin is needed.

Data

RSS and content ingest pipelines: conditional GET, dedupe, clustering, feed generation. Scheduled sweeps as oneshot units and timers, with the pacing stored as data.

Comms

Self-hosted mail — Postfix, Dovecot, OpenDKIM, relays — plus listmonk and PocketBase. SPF, DKIM and DMARC published and verified, not assumed.

Tooling

Hermes Agent plugins and MCP tool wiring. Scheduled jobs, watchers and monitors that page a human only when something is actually wrong.

nīlotpala · blue lotus

Tell us what you want built

One paragraph is enough. We answer everything that is not a bot.