announcement,

PromptWar̊e ØS Ships: Unix Architecture for Your AI Co-Founders

Huan Li Huan Li Follow Dec 13, 2025 · 4 mins read
PromptWar̊e ØS Ships: Unix Architecture for Your AI Co-Founders

Stop copy-pasting prompts. Start booting an OS.

We are entering the era of “Vibe Coding,” where the primary interface to software creation is natural language. Yet, our method for managing this interface is stuck in the stone age: scattered text files, copy-pasted “You are a helpful assistant” blocks, and fragile, project-specific configurations.

Today, we are introducing PromptWar̊e ØS, an LLM-Native Operating System designed to turn your chaotic prompt library into a structured, distributed, and bootable environment.


The Philosophy: English at Ring 0

PromptWar̊e ØS (PromptWare OS) is built on a radical premise: The Prompt is the Code.

In traditional computing, the OS manages hardware resources (CPU, RAM, Disk). In PromptWar̊e ØS, the “Hardware” is the Large Language Model itself.

  • CPU: The Inference Engine.
  • RAM: The Context Window.
  • Disk: The Distributed File System (Remote + Local).

We have applied the timeless principles of Unix Architecture to the fluid world of LLMs.

1. The Microkernel Architecture

Instead of a monolithic “Super Prompt” that tries to do everything, PromptWar̊e ØS uses a tiny, immutable Kernel (os/kernel.md). It defines the physics of the world but contains no personality.

It exposes System Calls—the primitives of the OS:

  • os_resolve(path): Maps virtual paths to real URLs.
  • os_ingest(library): Dynamically loads skills into the context window.
  • os_invoke(tool): Executes remote tools without polluting your workspace.

2. The One-Line Boot

Gone are the days of pasting 500 lines of context. To start PromptWar̊e ØS, you paste a simple Bootloader configuration:

# PromptWar̊e ØS Bootloader
root: https://shipfail.github.io/promptware/os/
kernel: /kernel.md
init: /agents/powell.md

The LLM reads this, fetches the Kernel, mounts the Virtual File System, and executes the init process (the Agent). In seconds, you go from a raw model to a fully configured AI Co-Founder.

3. The Zero-Footprint Protocol

We believe your workspace is sacred. Traditional agent tools often download scripts, create temp files, and leave a mess.

PromptWar̊e ØS enforces a strict Zero-Footprint Protocol. System tools (like image optimizers or git helpers) are:

  • Remote-First: They live in the cloud, not your repo.
  • Ephemeral: They are streamed directly to the runtime (e.g., deno run -A <url>) and vanish after execution.

Architecture Overview

The system mimics the classic Linux boot process:

  1. Bootloader (os/bootloader.md): The entry point. It instructs the LLM to Ingest and Adopt the Kernel.
  2. Kernel (os/kernel.md): The runtime. It enforces the “Law of Files” and provides the os_* system calls.
  3. Init (os/agents/powell.md): The first user-space process. This is your Agent (e.g., Powell, the Cartographer). It defines the persona and loads necessary skills.
  4. Skills (os/skills/): Shared libraries (like /usr/lib). These are modular capabilities (Jekyll, Git, NPM) that any agent can load on demand.

Case Study: The Jekyll Skill

To see this architecture in action, look at our Jekyll Skill (os/skills/jekyll/SKILL.md). It acts as a standard library for managing blog posts.

Instead of complex instructions, it defines a simple Library Interface that maps natural language intents to Kernel System Calls:

Function Syscall Description
fit-image os_invoke(${root}/skills/jekyll/fit-image.ts) Resizes/converts image to WebP.

When the Agent decides to “optimize the image,” it triggers os_invoke. The Kernel then streams the fit-image.ts tool directly from the cloud, executes it using Deno, and wipes it from memory. The user’s workspace remains pristine.


Why This Matters

For the AI Engineer:

  • DRY (Don’t Repeat Yourself): Maintain your skills in one repo. Boot them everywhere.
  • Modularity: Swap out the init agent to change from a “Coder” to a “Writer” without changing the underlying OS.

For the Researcher:

  • Structured Context: Treat the context window like memory. Load and unload libraries dynamically to save tokens.
  • Reproducibility: Share a boot config, and anyone can replicate your agent’s exact state.

chaos-to-promptware


Get Started

PromptWar̊e ØS is open source and available today.

  1. Star the Repository: github.com/ShipFail/promptware
  2. Try the Bootloader: Copy the boot block from the README and paste it into your favorite LLM.
  3. Build Your Own Agent: Fork the repo and create your own init process.

Welcome to the future of AI interaction. Boot System.

Join Newsletter
Get the latest news right in your inbox. We never spam!
Written by Huan Li Follow
Founding Human & Architect | Author @ Wechaty, Silicon Adventist, Serial Entrepreneur, Angel Investor, Burner🔥