vegarsti

Radius current request flow

sequenceDiagram
    autonumber
    participant C as Client / Pi session
    participant G as Gateway Cloudflare Worker
    participant L as Account Ledger Durable Object
    participant U as Selected upstream provider

vegarsti

Radius message request sequence

sequenceDiagram
    autonumber
    actor User
    participant Pi as pi CLI/TUI
    participant Ext as Radius provider extension<br/>(pi-provider.ts)
    participant Gateway as Radius Gateway Worker<br/>radius.pi.dev
    participant Catalog as Gateway Catalog<br/>(DO/storage)

vegarsti

import type { ExtensionAPI } from "@mariozechner/pi-coding-agent";

export default function (pi: ExtensionAPI) {
	pi.on("session_start", async (_event, ctx) => {
		ctx.ui.setFooter((tui) => {
			const interval = setInterval(() => tui.requestRender(), 100);
			return {
				dispose: () => clearInterval(interval),
				invalidate() {},
				render(): string[] {

vegarsti

#include <sys/event.h>
#include <sys/time.h>
#include <fcntl.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

// Watches files for changes and prints which file changed
int main(int argc, char *argv[]) {
    if (argc < 2) {

vegarsti

S3 File Storage: Current State & Plan

Where files are stored in S3

All files go to the lefos-conversations-dev bucket (config: CONVERSATION_BUCKET), with one shared S3 client at packages/elwing/src/s3/client.ts.

S3 key hierarchy:

{domainId}/{mailboxId}/{conversationId}/
├── artifacts/{filename} # Agent-produced files

vegarsti

Elwing Billing System — Data Flow Summary

Elwing uses Polar (polar.sh) as its billing/subscription provider. Billing is credit-based: users purchase subscriptions or top-ups via Polar, receive credits, and credits are consumed as the AI agent processes emails, chats, and memory operations.

Key Concepts

Concept	Description
Credits	Internal currency. Converted from token cost: credits = tokenCents × 12.5
Billing Owner	Each space has one billing owner (user). All charges in that space bill to them.

vegarsti

Session Storage Record Examples

Each example shows the concrete conversation_records rows written per trigger type. All examples use conv_ABC as the conversation ID.

---

Common: Session Root

Written once per conversation (lazily, on first trigger). All subsequent main-thread

vegarsti

Session State Migration Plan

Move all session state out of Absurd checkpoint tables into our own database, enabling conversation replay and forking from conversation_records + a new session table.

Phase 1 — Refactors (no DB changes)

1a. Move DB recording inside ctx.step

vegarsti

https://twitter.com/thorstenball/status/1576619567488475137?s=20&t=KaBdUrc5-M1bnNTMU6tuQA

Working with Unix Processes
Working with TCP Sockets
Working with Ruby Threads
Zed Shaw's C book
Programming From The Ground Up
Destroy All Software
PeepCode Play by Play
Pragmatic Programmer

vegarsti

Install Karabiner Elements.
Follow this
https://github.com/tekezo/Karabiner-Elements/issues/638