open source from ktesio

Tools for the agents you run.
Built in the open.

Ktesio is a software company in Rotterdam doing agentic AI and platform engineering for production. This is its open-source work: tools for the AI agents you run on your own machines. All of it is public, down to the design notes.

Hekma · bite every repository on GitHub

pay-triage crosses its budget hekma 0.11.0
hekma agent logs pay-triage --follow
2026-10-31T22:16:46Z [agent-out] session started (pid 65728)
2026-10-31T22:16:46Z [engine] engine: starting -> running
2026-10-31T22:16:47Z [agent-out] PAY-2281 refund stuck in pending: routed to billing
2026-10-31T22:16:47Z [agent-out] KTESIO_USAGE {"sequence": 0, "input_tokens": 31420, "output_tokens": 2610}
2026-10-31T22:16:48Z [agent-out] PAY-2282 duplicate charge: routed to disputes
2026-10-31T22:16:48Z [agent-out] KTESIO_USAGE {"sequence": 1, "input_tokens": 28870, "output_tokens": 3120}
2026-10-31T22:16:49Z [agent-out] PAY-2283 card declined at checkout: answered, closed
2026-10-31T22:16:49Z [agent-out] KTESIO_USAGE {"sequence": 2, "input_tokens": 33910, "output_tokens": 2480}
2026-10-31T22:16:50Z [agent-out] PAY-2284 invoice in wrong currency: routed to billing
2026-10-31T22:16:50Z [agent-out] KTESIO_USAGE {"sequence": 3, "input_tokens": 30150, "output_tokens": 2890}
2026-10-31T22:16:51Z [agent-out] PAY-2285 chargeback notice: needs a human
2026-10-31T22:16:51Z [agent-out] KTESIO_USAGE {"sequence": 4, "input_tokens": 29640, "output_tokens": 3310}
2026-10-31T22:16:51Z [engine] engine: running -> paused (breach: cumulative tokens)
• note: Agent Instance 'pay-triage' is paused; no further output until it is resumed.
hekma 0.11.0, recorded on . pay-triage is a stand-in: a script that prints ticket lines and reports usage without calling a model, run under a small host on Hekma’s engine. The supervision, the metering and the pause are Hekma’s. Hekma’s adopt-and-release notices are left out.
2 projectsopen source, on GitHubRustand Swift for bite's helperApache-2.0 · MITlicencesbite 0.5.0latest release,

projects

2 open source

Hekma

The control plane for agent workloads.

One way to run, see and steer the AI agents you run. Today it supervises them, meters the tokens they spend and pauses the one that crosses its budget the moment it does. Runs, Policies and wire control are being built in the open. A Rust CLI, and an engine you can embed in your own host.

curl -fsSL https://cli.ktesio.dev/hekma/install.sh | sh
version
0.11.0
licence
Apache-2.0
written in
Rust
runs on
macOS · Linux · Windows
crate
hekma
roadmap
in developmentRuns, Policies and the long-running host, being built now.
pay-triage, after the pause hekma 0.11.0
hekma agent show pay-triage
▸ Runtime status for pay-triage (8 rows)
Field             Value                                           
──────────────────────────────────────────────────────────────────
State             paused                                          
Restart policy    on-failure                                      
Restart count     0                                               
Budget            cum 0/150000 tok (pause)                        
Usage (tokens)    cumulative in 153990 / out 14410; this run: in …
Cost (estimated)  — (no Rate configured — dollar features inert)  
Metering source   self-reported                                   
Supervision       detached                                        
• note: usage + budget are real TOKEN counts from the Usage Ledger (budget '—' means no budget configured); dollar figures appear only when a Rate is configured (cost.rate.input/output, optional cost.rate.cached) and are labeled estimates — with no Rate, dollar features are inert.
hekma 0.11.0, recorded on . The same agent after the pause, from hekma agent show. Budget counts down what is left of the cap: 0 of 150,000 tokens. Hekma’s adopt-and-release notices are left out.

on crates.io

  1. 0.11.0
  2. 0.9.0
  3. 0.8.1

all releases on GitHub

bite

Native Apple apps for AI agents.

Calendar, Reminders, Mail, Notes, Contacts and Messages as MCP tools, each with a matching CLI verb. Every call goes through Apple’s own APIs via a Swift helper — no osascript processes — and bite makes no network calls of its own.

cargo install bite-mcp

Needs the Xcode Command Line Tools. Then run bite setup.

bite is an independent project, not affiliated with or endorsed by Apple Inc.

version
0.5.0
licence
MIT
written in
Rust · Swift
runs on
macOS
crate
bite-mcp
roadmap
phase 2 plannedPhase 1, the core apps, shipped; phase 2 is planned.
bite --help bite 0.5.0
bite --help
bite: a Rust control plane over a native Swift helper (EventKit + ScriptingBridge).
Run `bite mcp` as an MCP stdio server, or use the verbs directly.
Usage: bite [OPTIONS] <COMMAND>
Commands:
  mcp             Run the MCP stdio server (this is what agent CLIs launch)
  setup           Interactive onboarding: install helper, check permissions, configure agent CLIs
  doctor          Check environment, helper and per-app permissions (prompt-free by default)
  install-helper  Install/refresh the native helper at its stable path (TCC-friendly)
  helper          Bridge diagnostics
  config          Read/write bite config
  calendar
  reminders
  mail
  notes
  contacts
  messages
  index
  search
  mail-bulk
  help            Print this message or the help of the given subcommand(s)
bite 0.5.0, recorded on . bite --help: the MCP server, setup and doctor, then a verb per app.

on crates.io

  1. 0.5.0
  2. 0.3.0
  3. 0.1.1

all releases on GitHub

design notes

4 public documents
  1. bite

    Roadmap 

    Phase 1, the core apps, shipped; phase 2 planned; and what bite will not do.

  2. bite

    Bridge & handoff protocols (Rust ↔ Swift) 

    The line-delimited JSON contract between the Rust control plane and the Swift helper, and the file-based handoff to the crawl worker.

  3. bite

    Implementation plan (as built) 

    One published crate, one binary, Swift helpers for Apple’s frameworks: the architecture as it shipped.

  4. Hekma

    Architecture 

    A tour of the Rust workspace, the install flow and the file-based project state.

Public, down to the design notes: the documents behind the tools, why they are built the way they are, what their parts promise each other and what comes next, each dated the day it first landed in its repository.

essay

Metering agents you don't control 

Why Hekma meters an agent's model traffic at a boundary the agent cannot bypass, how the loopback proxy, the Usage Ledger and budget enforcement fit together, and what the meter still cannot see.

The number a budget acts on has to come from a boundary the agent cannot bypass, cannot forget to update, and cannot round down to zero.

read the essay

published
by
Islam Magdy
project
Hekma
reading time
11 min

elsewhere