Practical infrastructure for long-running AI-agent work.
Continuation, recovery, operator control, multi-agent tooling, auditing, packaging, messaging, quota awareness, and Windows-first utilities built around one boring but important idea: useful work should survive the end of a chat session.
The builders change. The work continues.
Project map · Brand & links · Contributing
SAIPEN is a vendor-neutral continuation protocol for AI coding agents. Project state lives beside the code in plain files, so a cold agent can recover the current task, constraints, history, and exact next action without depending on one provider's chat memory.
SAIPEN HQ is the umbrella for that protocol and the surrounding tools that make agent work easier to operate, inspect, resume, and verify.
Repository ownership today: the projects below are currently hosted under
vacterro. SAIPEN HQ is the organization and ecosystem home. A project should only be described as organization-owned after an actual GitHub repository transfer.
| Project | Purpose |
|---|---|
| SAIPEN Core | Plain-file continuation protocol, recovery model, validation, and cold-agent handoff. |
| SAIPEN Website | Official static documentation and public web surface for the protocol, rendered in the Wintage design system. |
| ZAICODE | Windows operator workbench for running many AI coding agents and projects from one control surface. |
| FastPrompter | Local-first keyboard scratchpad, prompt/snippet workspace, and file-container tool for Windows. |
| LIMISAW | Read-only quota monitor for Codex, Claude Code, Antigravity, and Zcode. |
| SAITULS | Windows utility hub and Explorer context-menu toolkit. |
| SAIPENVIEW | Visual control center for SAIPEN projects, tickets, conformance, and agent workflows. |
| Project | Role |
|---|---|
| AUDAPACK | Verified ZIP packaging, multi-wave audit handoff, and browser bridge. |
| SAIPAL | Forensic protocol observer for session drift and root-cause evidence. |
| SAIMAIL | Local-first agent post office with sealed messages, provenance, and bounded triage. |
| SAICONT | Fail-closed Windows console watcher for bounded AI-agent recovery and resume. |
| SAIPET | Read-only internet scout that finds relevant problems and drafts human-approved replies. |
| SAIPLAN | Human-facing SAIPEN-style planner with explicit tickets, dependencies, and durable Markdown state. |
| SAITALK | Portable response-behavior contract for humans and AI agents. |
| SAIWORK2 | Tauri desktop control plane for coding agents, queues, sessions, and SAIPEN-aware workflows. |
SAIPEN HQ also connects to a wider set of practical utilities built by vacterro, including ProTrail, Problip, Wintage, VACZEN Calendar, and several creative/media automation tools.
They are not all SAIPEN protocol components. They share the same project network, community, and general bias toward local control, explicit state, automation, and recoverable workflows.
- State should survive sessions. Important work belongs with the project, not only in model memory.
- Local-first where practical. Tools should remain inspectable and useful without a mandatory hosted backend.
- Explicit beats magical. Human-readable files, visible state machines, logs, and contracts are preferred over invisible behavior.
- Recovery is a feature. Restarts, failed agents, exhausted quota, stale state, and interrupted work are normal operating conditions.
- Operator control matters. Automation should reduce babysitting without hiding what it is doing.
- Evidence over vibes. Tests, validators, provenance, and reproducible failure cases carry more weight than confident prose.
- Windows is first-class. Windows support is designed in, not stapled on after the interesting work is finished.
Discord: SAIPEN Community
Use Discord for quick questions, screenshots, ideas, and cross-project discussion. Use the relevant repository's GitHub Issues for reproducible bugs and durable feature requests. That split keeps chat conversational and engineering work searchable six months later.
There is no requirement to become a "community member" before contributing.
Useful contributions include:
- reproducible bug reports;
- minimal failure cases;
- documentation corrections;
- platform compatibility reports;
- design criticism backed by concrete examples;
- focused pull requests against the owning repository.
Project-specific contribution and security rules live in each repository and take precedence over this organization-level overview.
SAIPEN HQ is the ecosystem/organization identity.
vacterro is the current author and repository owner for the linked projects.
That distinction is intentional. It allows the organization to become a shared maintainer surface later without pretending the migration or governance already happened.
Persist the state. Verify the work. Let the next agent continue.
If these projects are useful to you, optional support: Buy Me a Coffee · Boosty · PayPal · other ways