Home / Blog / ClawDOS – An AI coding agent for DOS news update
Tech News

ClawDOS – An AI coding agent for DOS news update

Developer Ricapar launched ClawDOS, an AI coding harness built with Claude that runs on legacy DOS and an original 4.77 MHz IBM PC XT 5160 with 640 KB of RAM.

By Dillip Chowdary • Nov 21, 2026 • Source: ricapar.net

ClawDOS – An AI coding agent for DOS news update
Illustration · Pexels

At a glance

Product
ClawDOS
Primary executable
HARNESS.EXE
Target hardware
IBM PC XT 5160
System CPU
8088 at 4.77 MHz
System memory
640 KB RAM
Harness binary size
176 KB

Developer Ricapar launched ClawDOS, an artificial intelligence chat and coding harness engineered specifically to operate directly on legacy DOS running on an original IBM PC XT 5160, according to ricapar.net's report. The target hardware configuration pairs an Intel 8088 microprocessor clocked at 4.77 MHz with 640 KB of conventional system RAM and an original CGA display card. Built entirely through code written by Claude to test development boundaries under extreme hardware constraints, the runtime environment lets users issue natural-language programming instructions directly from a standard C prompt to inspect directories, write source files, execute native DOS builds, and review visual screen outputs.

This report examines how the autonomous coding harness operates across vintage hardware components, offloads cryptographic transport encryption, drives vintage compilation suites, and manages internal runtime memory boundaries. It is designed for software engineers, vintage hardware preservationists, systems programmers, and retrocomputing enthusiasts evaluating modern machine-learning agent protocols deployed onto severely constrained 16-bit processing architectures.

01Native harness execution and transport delegation

The runtime system operates directly from the IBM PC storage volume via two compiled DOS binary executables: the primary launcher CLAWDOS.EXE, sized at 29 KB, and the central system harness HARNESS.EXE, sized at 176 KB. The entire codebase comprises 13,000 lines of C and C++ source compiled with Open Watcom targeting the original 8086 instruction set. HARNESS.EXE speaks the Claude Messages API natively, handling outgoing payload creation, Server-Sent Events stream parsing, tool calling execution, and local disk-based transcript storage.

Because the vintage 4.77 MHz 8088 processor lacks computational throughput for modern cryptographic handshakes, network security responsibilities shift entirely away from the IBM PC hardware. Network packets travel through the local FreeDOS 1.4 system utilizing mTCP network drivers mapped to an NE2000 network interface provided by a modern PicoMEM expansion card. The 8088 machine handles ordinary raw HTTP transport, while a companion bridge computer running Python, socat, or stunnel proxies the plaintext traffic across port 443 via TLS straight to Anthropic's cloud endpoints.

Note: The proxy bridge host can manage and store the private API credential internally, completely preventing private key material from ever writing to the physical DOS disk image.

02CGA terminal interface and eighteen agent tools

The user interface delivers an 80-column terminal display using standard code page 437 typography rendered specifically for CGA video hardware. Visual output routines synchronize writes strictly to screen raster retrace periods, eliminating visible video snow artifacts, while hardware display scrolling runs directly via CRT Controller register start addresses. Background processing indicators and operational clock counters bind directly to system timer interrupt vectors, keeping clock counts updating cleanly while heavy background operations execute.

The model manipulates system storage, low-level architecture components, and vintage peripheral hardware through an internal suite of eighteen dedicated native tools:

Tool categoryTool functionsOperational scope
System and storagesysinfo, dir, read, searchQuery system parameters, inspect paths, read hex or text, scan strings
File modificationwrite, edit, delete, mkdir, renameCreate directory structures, write files, replace source code in place
Execution enginerunExecute batches up to twelve commands with timed screen capture
Hardware accesspeek, poke, portRead or modify direct physical memory addresses and hardware ports
Peripheral mediaplay, textartRender 16-color CP437 art, trigger PC speaker sound sequences
Persistent statememory_list, memory_read, memory_writeRead and store project context notes in C:\MEMORY

Built-in safety features remain active by default, requiring operator approval prompts via interactive yes-or-no key inputs prior to file, memory, or port mutations until toggled using function key F3.

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

03Automated program compilation and visual verification

ClawDOS autonomously orchestrates multi-file development cycles utilizing local vintage developer toolchains stored across the primary disk. A single conversational prompt requesting a prime-number calculation routine triggers ClawDOS to inspect its built-in machine compiler manuals, write PRIMES.C, invoke Turbo C, link the binary, and execute the final output in 64 seconds total, with 26 seconds dedicated strictly to native compilation and execution steps.

For complex graphics or sound verification, ClawDOS executes automated visual inspections utilizing native timer interrupt hooks that read raw video buffer allocations during execution. During testing for WarGames, an original tribute demo written entirely by the model across five source files and 15 KB of Turbo C code, a system capture hook dumped 320x200 4-color CGA video RAM 25 seconds into program execution. The 8088 processor compressed the uncompressed framebuffer into a 16 KB PNG image, forwarding it back into the cloud API message context for agent inspection.

  1. Query machine compilers to establish build parameters and target directories.
  2. Generate source files across local storage volumes using targeted tool edits.
  3. Trigger native build suites through batched DOS run tool commands.
  4. Capture screen memory using timer interrupt hooks to verify execution states.
  5. Inspect compiler transcripts to diagnose errors or complete execution tasks.

04Memory swapping and runtime footprint control

Conventional memory constraints require aggressive memory reallocation schemes whenever the agent hands execution over to native development software. Normal child programs spawned beside the active harness receive up to 200 KB of conventional memory inside the machine's 640 KB total limit. Whenever an intensive compilation workflow like Turbo C runs, the agent saves its complete working state, fully steps out of system memory, and releases roughly 450 KB of conventional RAM for native linking operations.

Once compilation terminates, the harness re-enters memory space, picks up the previous conversational thread, and continues execution with standard output messages in hand. Storage operations and network hardware remain managed through a plug-in PicoMEM card, which supplies system EMS support, real-time clock functionality, microSD storage virtualization replacing a disconnected physical 20 MB mechanical drive, and an emulated NE2000 network adapter interface.

Hardware-level reliability and codebase durability undergo automated validation runs across multiple platforms before physical hardware deployment. The test suite includes 31 boot validations run inside DOSBox-X against simulated mock API endpoints, native unit verification routines built for standalone DOS environments, and continuous software test runs executed within an emulated 8088 machine inside 86Box.

05Context caching and flight recorder telemetry

Network communication efficiency remains paramount over narrow 8088 bandwidth channels, making heavy use of modern API capabilities to sustain low network loads. Base system prompt instructions and available tool definitions take advantage of cloud prompt caching, ensuring ongoing conversation passes require minimal payload transfers. Once an initial exchange concludes, standard tool responses travel across the wire in payloads measuring approximately 500 bytes.

The system maintains continuous operational logs inside CLAWDOS.LOG, recording timing metrics and token budgets across every conversational interaction. Telemetry records document time to first token, upload payload sizes, incoming token counts, output volume, cache read volume, and total time away during external program builds.

Model selections and thinking intensity levels remain configurable mid-session via interactive hotkeys without interrupting active threads, while disk-backed JSON transcripts preserve full state integrity across surprise power disruptions. Base OS: FreeDOS 1.4 Codebase size: 13,000 lines of C and C++

Frequently asked questions

What physical hardware is required to run ClawDOS?

It runs on an IBM PC XT 5160 with an Intel 8088 CPU at 4.77 MHz, 640 KB of RAM, a CGA graphics card, and a PicoMEM expansion board for storage and network emulation.

How does an 8088 computer connect to modern secure APIs?

The IBM PC XT communicates over plain HTTP through mTCP to a companion bridge computer running a Python script, socat, or stunnel, which handles outbound TLS encryption to Anthropic's endpoints.

How does ClawDOS compile large programs with limited RAM?

ClawDOS serializes its operational state to disk and drops out of memory to allocate roughly 450 KB of free conventional RAM to compilers like Turbo C, automatically reloading when the compilation finishes.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →