IVAN (Intelligent Virtual Autonomous Navigator) is a single-file, browser-native autonomous agent console built by Xaeon under the RTBNXH umbrella. It is the first working artifact of the AI Agents domain within the 8IE8IE Engine.
IVAN is not a chatbot. It is a task executor. You give it a goal, and it plans, reasons, calls tools, and iterates until the job is done — or until it hits its step limit. Everything runs client-side in a single HTML file. No backend, no server, no build step. Drop it in a browser tab and it works.
It carries the RTBNXH philosophy directly: Function > Fluff. Build the thing. Make it work. Put it in people's hands.
What It Does IVAN runs an agentic loop — a cycle of think → act → observe → repeat — backed by your choice of LLM provider. On each turn it can:
Tool Purpose js_execute Run sandboxed JavaScript and return the output file_write Write files into an in-memory workspace file_read Read files back out file_list List everything in the workspace web_search Search Wikipedia for factual lookups planning Create, update, and track a step-by-step plan terminate End the run with a final summary The rail on the right shows the live plan, which tools are firing, and the current workspace contents — so you can watch the agent think.
Supported Providers IVAN ships with a provider registry covering Anthropic, OpenAI, Google Gemini, xAI, DeepSeek, Mistral, Groq, OpenRouter, Together, Cohere, AgentRouter, and Ollama (local, no key required). Pick one, paste a key, choose a model, go.
How To Use It Open the file. Save Ivan V2.html anywhere, open it in a modern browser.
Open SETTINGS (top right).
Pick an active provider from the dropdown.
Paste your API key into that provider's row. (Ollama needs none.)
Set MAX STEPS (default 15) and TEMPERATURE (default 0.4).
Close settings. The badge in the header confirms your provider and model.
Type a task into the input bar and hit RUN.
Example prompts:
"Write a fizzbuzz in JS, save it to fizzbuzz.js, then run it and show me the output."
"Search Wikipedia for Fractal Bitcoin, summarize the three most important facts, and save them to notes.md."
"Build me a plan to design a small synth, then execute step one."
STOP interrupts a run mid-flight. CLEAR CACHE & RESET wipes local storage and returns the whole console to a blank slate.
On Persistence By default, nothing is saved. Refresh the page and everything is gone — keys, workspace, plan, conversation. Two opt-in toggles let you persist provider settings/keys and workspace files to this browser's local storage (device-only, never transmitted). Both are off. Both are a tradeoff. Read the note in the drawer before flipping them.
Known Constraints Some providers block direct browser calls (CORS). Anthropic, OpenAI, Gemini, Groq, OpenRouter, and AgentRouter are the most reliable from a plain tab. Ollama works locally but needs OLLAMA_ORIGINS=* set so it will accept browser requests.
The Fractal Bitcoin Ordinal Attempt IVAN was inscribed as an Ordinal on Fractal Bitcoin as an early experiment in putting real, functional software on-chain — not a collectible, not a JPEG. A working agent console, stored as an inscription.
The attempt is not yet fully functional in that environment. Ordinal inscription and retrieval work, but running a live agent loop from an inscribed artifact raises questions the current tooling doesn't cleanly answer yet: how to handle API keys without embedding them in the inscription, how to route CORS-restricted provider calls from an immutable artifact, how to reconcile "the file never changes" with "the agent needs live network access." These are solvable. They aren't solved yet.
This is the point. 8IE8IE exists to treat protocol work as a first-class domain, and IVAN on Fractal Bitcoin is one of the first probes into what "AI agents as on-chain primitives" actually means in practice. The inscription is live. The functionality is coming.