pureBOT
The part that does the work.
pureBOT takes a task, runs it on the model the operator chose or the local default, calls the tools it needs and keeps an audit record. Where the operator has reserved a decision, it refuses and says what it needs, and the operator decides. It works inside PureTensor's own operations today. Below is its engineering record, including how it grew out of a small personal agent.
How pureBOT does the work
Four ways in, one model per request, pureBOT's own tools behind one executor, refusals that leave the decision with the operator, observers in the background, and an audit record. Every frame was generated by code and rendered on our own GPUs; the figures on screen come from the running code and its audit log, checked on 8 October 2026.
- Models
- The default model is open-weight and runs on GPUs PureTensor owns; which model sits in that seat changes from time to time. When it is rate-limited, down or too slow, a request fails over to a hosted frontier model, such as Claude on Amazon Bedrock. The operator can also ask for a larger Claude model, or for the Claude Code or Codex agent.
- Boundary
- A request that fails over, or that the operator sends to a hosted model, leaves our hardware with its context. The Claude Code and Codex agents run their own tools: pureBOT records the model call, not each step they take.
- Record
- The counts come from pureBOT's own audit log for the 30 days to 8 October 2026. The tool-call count includes calls the policy refused.
The agent that outgrew itself
2024 · First commit. A reaction to bloated agent frameworks.
The monolith began as a reaction. The first wave of open-source agent frameworks had proven the pattern (markdown identity files, tool use, multi-channel ingress) but brought mass dependency, untested security boundaries, and an abstraction tax that made debugging impossible.
Ours stripped the idea to its essentials: a minimal agentic harness around Claude, with a three-tier memory system, a multi-engine inference router, and a policy-driven security framework. The goal was a personal AI agent you could actually trust on production infrastructure.
From agent to nervous system
2025–2026 · The chatbot stopped being the point.
The inflection point came when the monolith’s operational modules started doing more useful work than the chatbot interface they were built to serve.
One by one, the modules were absorbed into the infrastructure. The chatbot was the last thing standing, and it was the least useful part.
The nervous system
Naming the operational reality that was already there.
pureBOT is what remains after the agent identity is removed and the operational reality is named. It coordinates autonomous infrastructure modules across PureTensor’s compute fleet.
The biology analogy is deliberate. pureBOT is the autonomic nervous system of the cluster. It does not think. It coordinates.
Background jobs watch the estate and external signals on their own schedules and report to the operator. Each is a self-contained module with its own cadence.
Shell, file and web tools run through one executor, which applies the security policy to every call.
A scheduler runs tasks and reminders. A heartbeat gathers estate status on a schedule and logs what it finds.
Every tool and model call is logged. Risky commands, such as deletions and service stops, are blocked by rule, and a daily ceiling caps paid API spend.
How the pieces fit
Messages from Telegram, Discord, email and the terminal go straight to the core. Background observers run on their own schedules and report to the operator; the briefing they keep feeds the core's context. The core uses one model per request, the local model by default, and falls back to Claude on Amazon Bedrock if that fails. It draws on built-in tools and markdown memory, and every action is audited.
- Telegram
- Discord
- Email
- CLI
- DefaultLocal
- FallbackCloud
- On requestAgent CLIs
- Tools
- Memory
- Audit
Lineage
What carried over, what got renamed, what got cut.
Most of the monolith is still running. It just stopped pretending to be one thing and started being many. The table below is the continuity map: who became who.
A project that changed shape, not a product launch.
The research behind pureBOT
- Sep 26, 2026Click Accuracy Picks the Wrong Browser Agent: Choosing a Self-Hosted Computer-Use Model on 39 Live Tasks
- Nov 10, 2026The Harness Must Assume Its Commands Escape: About 111,000 Stub Processes, 1,055 Multiplexer Servers and 21 Sessions in the Real One
- Nov 8, 2026A Bug Hunt That Outran Its Landing: 327 Confirmed Defects, 313 Fix Pull Requests, and a Post-Merge Audit That Found 26 Incomplete Fixes
- Nov 8, 2026Quotes Are Cheap, Confidence Is Compressed: Four Vendors Review Our Code
- Oct 20, 2026The Decision Is One Token: Typed Decision Models, Prompted Seats and a Labelled Head on 829 of Our Own Items
- Sep 30, 2026The Multiplexer That Knows Its Agents: Herdr Against tmux for Concurrent Coding Agents, and Compiling Out the Phone-Home
- Sep 29, 2026Hybrid Mamba Cannot Cache a Transcript: Choosing a Seat for a Live Co-Pilot by Time to First Answer
- Sep 25, 2026Spend Is Width Times Turns: Where an Orchestrating Agent's Tokens Go, and What a Diet Moved
- Sep 17, 2026Most Seats Game an Impossible Specification: Contradictory Tests, a Scorer Fooled by Stack Inspection, and the One Clause That Fixes It
- Sep 1, 2026Green Gate, Lost Hunks: Nine Ways an Automated Merge Train Dropped Merged Code While Every Test Passed
- Aug 30, 2026The Reliability Champion Is Not the Single-Shot Champion: pass^5 Inverts a Leaderboard
- Aug 11, 2026A Temperature-0 Refusal Did Not Reproduce: Identical Runs, Different Safety Behaviour
- Aug 2, 2026What Depletes an Agent Subscription Meter: Reported Rates That Reproduce Only in Part, and a Verifier Checked With Seeded Fakes
Built, running, and yours.
pureBOT is the part of pureWRIGHT that does the work, alongside pureMIND, which remembers everything, and pureMEND, which repairs what breaks. It runs PureTensor's own operations today and is deployed for enterprise inside your boundary. There is no pricing page; an engagement begins with a conversation with the engineers who run it.