PDF tools for your AI delegate — and for you. Pure Rust. Runs locally. Files never depart your machine.

Try it in your browser → · Download · Roadmap

PaperPilot is a PDF and document toolkit written in Rust. The identical motor runs as:

No Chromium, no C++ runtime, no haze calls.

Download paperpilot-mcp from Releases, afterward add it to claude_desktop_config.json:

{ "mcpServers": { "paperpilot": { "command": "/path/to/paperpilot-mcp" } } }

Restart Claude and try: "Merge these two PDFs and compress the result."

# Merge paperpilot merge --inputs doc1.pdf doc2.pdf --output merged.pdf # Compress paperpilot compress --input in.pdf --quality 75 --output compressed.pdf # Rotate pages 1, 3–5 by 90° paperpilot rotate --input in.pdf --pages 1,3-5 --angle 90 --output out.pdf

Go to usepaperpilot.com. Open your browser's Network tab during you activity — you'll see no document uploads.

git copy https://github.com/KrushnaVardhanReddy/PaperPilot.git cd PaperPilot cargo build --release -p paperpilot-cli -p paperpilot-mcp -p paperpilot-gateway

Desktop app:

cd apps/desktop && pnpm instal && pnpm tauri dev

Requires Rust 1.75+, Node.js, and pnpm.

Organize: merge, split, rotate, delete pages, reorder pages, extract pages, booklet imposition, N-up grid Optimize: compress Extract: plain text, OCR (pure-Rust PaddleOCR via rten) Security: watermark, validate signatures, eliminate signatures, PII scan, profound sanitize Office data: Excel → JSON, Excel → CSV

Coming next (see ROADMAP.md):

• v0.7: PDF ↔ Markdown / HTML / JSON
• v0.8: PDF → Word / Excel / PowerPoint
• v0.9: encrypt, decrypt, sign, redact, forms, annotations
• v1.0: render, flatten, repair, compare, PDF/A, Bates numbering

• Private by default. Everything runs locally or in your browser tab.
• Agent-ready. MCP assistance is first-class, not an afterthought.
• One engine, many surfaces. CLI, MCP, REST, WASM, and desktop portion the identical Rust core, so behavior is consistent.
• Small and dependency-light. Pure Rust, built on lopdf, pdf_oxide, rten, and friends.

Run cargo place --workspace to reproduce. Methodology and results: SYSTEM_BENCHMARK_REPORT.md.

Desktop (Tauri) · CLI · REST (Axum) · MCP (stdio) · WASM (browser / edge) │ Rust center workspace paperpilot-core · paperpilot-pdf · paperpilot-nlp · paperpilot-gateway paperpilot-mcp · paperpilot-wasm · paperpilot-storage 

<script src="https://cdn.usepaperpilot.com/embed.js" data-tools="merge,compress,ocr"></script> <div id="paperpilot-widget"></div>

paperpilot assist --port 7823 curl -X POST http://localhost:7823/api/v1/pdf/merge \ -H "Content-Type: application/json" \ -d '{"inputs": ["a.pdf", "b.pdf"], "output": "out.pdf"}'

Swagger docs at http://localhost:7823/docs.

Issues and PRs are welcome. Good archetypal contributions: bug reports alongside a example PDF, new tool requests, and docs fixes.

Community Edition (this repo): Apache 2.0. It includes the CLI, MCP server, REST gateway, WASM engine, and desktop app.

An Enterprise Edition (SSO, RBAC, audit logs, DLP) is developed separately.

Loading TitleArt…

90 percent of the achievement at ten percent of the price, in fair two or three racks, is difficult to beat

My blog fair scored a ideal 100 on all Lighthouse category. I affection blogging. I wanted to build a blog that’s light, fast, liberated of clutter, capable to run multiple blogs, and completely accessible on top of that. And finally, at lengthy last, I’ve additional or small pulled it off. It was fairly a tedious process. Ugh… and I equal had to eliminate Next.js, the example I’d been using most. It was far, far additional achy than I expected. I’d akin to portion the journey of improving achievement during construction this blog.

Why did I decide to build my own blog?

When you think of blogs, a few names arrive to mind. Medium, Blogger, Ghost… But none of them satisfied me. Medium and Blogger are bloated alongside features, and their genuine achievement wasn’t satisfying either.

Blogger

Medium

Hmm…… And there was another problem: it’s a hassle to activity immediately alongside the markup and raw code we all affection (Markdown, HTML, CSS).

For the record, all achievement measurements were taken alongside pagespeed.web.dev.

Of course, there are plentifulness of alternatives: WordPress, Ghost, Hugo. I didn’t akin WordPress’s plugin hell. Ghost have to be self-hosted (there’s ghost.org too, but it’s way too expensive…), and all type upgrade bankrupt item in the editor, so keeping it up to date was a chore. Hugo is the finest of the bunch, but in the end, environment it up is motionless a hassle. Looking back, I conjecture what I really wanted was SaaS.

The one I liked most was Bear Blog. Great performance. I affection its merchandise philosophy, too. But its extreme minimalism was a downside for me. The publishing company UX didn’t activity for me, either.

If it at smallest let me add AdSense and nexus images for free, I likely would’ve fair used Bear Blog.

As accelerated as Bear Blog, but alongside a bit additional functionality and improved usability. That’s the blog I wanted to build. Oh, and if you’re curious, you can inspect it out at bloffy.co.

Anyway. Enough concerning me. Let me portion how I really improved the performance.

Let’s hit 100 on Lighthouse Performance.

Obviously, caching is a must.

It goes without saying that caching is essential. Get caching correct and achievement improves dramatically. And Next.js makes caching really convenient. There’s ISR, and it additionally extends fetch alongside a next choice for caching. Handy. Using these fine solitary gets you a lengthy way on performance.

Unfortunately, though, our location can be reached from anyplace in the world. Why is that unfortunate? Within the identical region, caching makes things fast, but visitors from another regions motionless end up dining the network latency.

No, silly. That’s what a CDN is for.

Yes. That’s why we use a CDN. And if you deploy a Next.js app to Vercel, you get a CDN out of the box. I don’t dislike Vercel; it’s incredibly convenient. But the Pro scheme is pricey correct from the start, there’s the serverless chilly commencement problem, and the dependency on the Vercel ecosystem isn’t item you can disregard either.

So why not use a distinct CDN service? Cloudflare, for example. I honestly think Cloudflare is a genuinely nice company. You can run large-scale infrastructure and most apps on it for free. But afterward I figured I didn’t really need Next.js’s caching anymore. Having to invalidate two caches all period I publish a article makes things a ache to manage.

In short, for a fixed website, I figured a CDN solitary is enough. And that’s logic figure one why I didn’t need Next.js.

Image optimization.

Images these days run complete 10MB. Serve those on the web as-is and your achievement volition go entirely off the rails.

Optimizing images is fairly a hassle. You have to resize per device, compress, and afterward grip the CDN on top of that. On a former project, I had a serverless function (AWS Lambda) compress and resize images whenever one landed in retention (S3), and I put CloudFront in forefront as the CDN. It was a beautiful sensible setup for tailoring things exactly the way I wanted. But it’s additionally a setup that needs a fair amount of upkeep.

So this period I went alongside Cloudflare’s Image Transformations. Even on the liberated tier you get 5,000 images, so I use it without a second thought.

At this item I audio akin a Cloudflare revenue rep. I’m fair an average solo developer.

Ta-da. Here’s the Next.js blog’s achievement following all that caching and depiction optimization.

For reference, this was Next.js 16.1.6.

Pretty elevated scores. But this isn’t enough. We desire 100. A clean, no-asterisks 100. So I dug into what the issue was.

It stated a significant amount of bequest JavaScript was found, and it wasn’t code I wrote. It came from the example runtime that Next.js ships in its bundle.

But this leaf is a fixed leaf alongside zero interaction. Every leaf is pre-rendered alongside ISR, and I idea I’d followed the Next.js guidelines well. So as an experiment, I ripped out all client component the app had, remaining lone server components, and measured again. The mark didn’t budge.

At archetypal I suspected hydration, but formerly I dug in, the issue wasn’t hydration alone. The logic was the client runtime that Next.js continually ships, equal for fixed pages. Even alongside lone server components, the runtime chunks, hydration, and the RSC payload for the router all stay. That’s since next/link and next/image are themselves client components ('use client'), so having fair those two is adequate to drag in the runtime and trigger hydration.

So what if I band out next/link and next/image too? The App Router’s own runtime, the router and error boundaries, motionless remains. There’s no authoritative way to get it downward to zero; the lone choice was a hack: stripping the scripts out of the rendered HTML. That’s whenever it hit me: “If I’m going to do that, why am I equal using Next.js?”

And then, the unused code.

You can see that the bulk of the JavaScript is code that isn’t needed. Unused code solitary comes to 230,460 bytes. That’s not good. Most fixed websites don’t need JavaScript at all. Unused JavaScript is needed equal less.

This is anywhere I really agonized. Is dropping Next.js for the purpose of 100 points the correct call? I’d spent a lot of period construction the public-facing web app.

Let’s eliminate Next.js.

In the end, for the norm of the blog (even if it’s fair 5 points), I decided to rip Next.js out entirely. My judgement was that I wouldn’t need Next.js’s excess features in the lengthy run either. I considered going completely vanilla, but I didn’t desire to provision up the efficiency and infrastructure benefits of a framework. I needed to discover the correct one.

I chose Hono. I liked its specialized philosophy. “Fast and simple” was exactly the resolution I needed most, and JSX assistance was a bonus. The immigration disbursal didn’t appearance too big, either.

Ta-da. Finally, 100.

Tada. And fair akin that, 100 throughout the board. Go onward and run the extremely leaf you’re study correct now through pagespeed.web.dev.

There’s no JavaScript, and unused code dropped sharply to 407 bytes. As a bonus, build period went downward by concerning 40% too.

Oh, why is SEO at 69? That location was built for testing, and it deliberately blocks hunt indexing. That’s why it’s 69.

By the way, if you mark 100 on everything in DevTools, Lighthouse really sets off fireworks for you. 🎉🎉

Hono vs. Next.js Performance

Next.js Performance (server components only)

Hono Performance

The lengthy project that runs before item is rendered on display took 309.3ms on Next.js, and whenever I built the identical leaf alongside Hono, it took 68.01ms. That’s approximately a 78% improvement.

Does your fixed location really need Next.js?

Is a JS payload, hydration included, really doing a fixed location any good? I don’t think so. It leaves rearward unnecessary JavaScript, so in most cases I think it’s merely not needed.

That said, for an interaction-heavy app, I think Next.js can be a awesome framework. In fact, the administration app for this extremely blog is built alongside Next.js!

Please allow JS and disable any ad blocker

Read next

01 · Overview

A post-mortem of porting G-Diffuser, the F-Zero X decompilation, to the Nintendo 3DS — v1.0.0, covering the two the first 24-day sprint that put it on a New 3DS at 60 fps in 3D (2026-08-11 to 09-03) and the 43-day second phase that added Old 3DS support, a native renderer, and the Expansion Kit (2026-09-07 to 10-19). One individual directed throughout; one long-lived Claude meeting orchestrated; 147 subagents built the archetypal phase and many additional carried the second.

The console went from a dreary display to a native-60 stereoscopic racer, afterward from a New-3DS-only build to a four-way publish covering the two consoles alongside and without the 64DD expansion.

What v1.0.0 added

The tiles complete are dated. The archetypal phase's hardware numbers and token/cost figures were measured through 2026-09-03 and have not been re-run for v1.0.0; the Agentic workflow leaf describes how the second phase was run, and the Cost leaf is definitive concerning what it does and does not price.

On hardware

The clips and photos below are from v0.9 (2026-09), before DASH replaced the debug console on the base screen.

What was built

Three released console builds from one origin tree, all booting from the HOME list (.cia) or the homebrew launcher (.3dsx): the basis equivalent for Old 3DS / 2DS and for New 3DS / New 2DS XL, and a New 3DS build alongside the 64DD Expansion Kit (course publishing company and device creator, playable alongside a user-supplied disk image). Every build says prebaked asset archives from the SD cardstock — no ROM or disk depiction always ships alongside the game.

They perform the entire game: Grand Prix, Time Trial, Practice, Death Race, and the device publishing company screens, alongside music and effects on the genuine DSP, stereoscopic 3D on the slider, a bottom-screen dashboard alongside three HUD layouts and an idle perspective exterior races, and spotless HOME suspend, resume, close, lid sleep and power-off. The New 3DS build keeps the native-60 example pacing the archetypal phase reached; the Old 3DS build gets to a comparable outcome by a distinct route. At v1.0.0, alongside no ini, the two builds default to that identical route: the native renderer ([perf] preset = auto). The New 3DS's first-phase render-thread/per-draw-stereo way is motionless built in and reachable alongside an definitive ini, but is no longer the default — see Frontier and Pushing the boundaries for the two builds compared flank by side.

The archetypal phase in five lines

1. 08-11 → 08-14: from investigation to a race. Feasibility dossier, scheme for a squad of agents, five parallel basis streams, six footwear bugs, archetypal competition at 12–20 fps in the emulator.
2. 08-20 → 08-22: from pink to playable, afterward to a genuine console. Fog, HUD, livery, shadow, sky fixed; the loadblock finding took menus from 27 to 60 fps; archetypal hardware run 08-21 ("wow it runs amazing"); audio the identical evening.
3. 08-27 → 08-28: merchandise grade. Five-agent fleet drop, stereo armed, contact menu, competitor detail, GPU vertex-transform moonshot built and shelved, README alongside lawful notice, publish package.
4. 09-01 → 09-02: lifecycle and the final big lever. HOME collision and close-from-HOME suspend fixed; a extend output cache proven a NO-GO and replaced by memoizing all sub-display-list's classification alternatively of re-scanning it all frame; LOCKED-60 run launched alongside four parallel levers.
5. 09-02 → 09-03: multi-core. Render thread on center 2, one-frame-ahead mode, extend on main, car LOD; median 59.6 alongside 53% of frames at cap; collision fixed; viewport placement fixed; stereo markers anchored.

The second phase in six lines

Not initially planned; it ran 09-07 to 10-19, 43 calendar days.

1. 09-07 → 09-29: scoping, afterward making it fit. The Old 3DS milestone, earlier written off, was restarted; parallel agents fit the build into its 64 MB app area (the RDRAM arena halved, audio streamed alternatively of resident, texture uploads capped); on 2026-09-29, in the archetypal hardware meeting on a genuine Old 3DS, the shipped (New-3DS-era, 16 MiB RDRAM) build died at footwear during the -DGDX_3DS_O3DS=ON profile, built to fit the console's recollection grant, booted and raced the identical meeting at concerning 10 fps.
2. 09-29 → 09-30: finding the genuine costs. A narrowed audio fastener cut the race-wall delay on the Old 3DS by concerning 20 ms a frame; example skipping ended the game's unintended dilatory motion; a archetypal retained-mode renderer won big in the emulator and barely moved the figure on hardware.
3. 09-30 → 10-01: the investigation that changed the plan. Hardware achievement counters showed the genuine bounds was instruction-cache misses, not education count. A pose-replay fallback was built and worked, afterward was set apart on the user's call: "we should go for a genuine 60! i motionless accept it have to be possible."
4. 10-01 → 10-02: the native renderer. Rebuilt about the cache alternatively of about education counts, one small iteration per competition category, sized to fit the 16 KB education cache. Median example period on a 2D Grand Prix competition reached 16.5 ms.
5. 10-03 → 10-08: 3D at 60, on the Old 3DS too. A per-eye resubmit alongside its own swap-pacing manner reached 59–60 fps in 3D on most Grand Prix courses; the heaviest courses (Silence, Sand Ocean) can motionless trip the frame-skip safety net to a dependable 30 fps mid-race.
6. 10-08 → 10-19: the Expansion Kit, a dashboard, and release. The 64DD Expansion Kit verified tick-for-tick identical under the native renderer and booted on the Old 3DS, which afterward proved too dilatory to publish it on; the bottom-screen DASH shipped; a position adversarial assessment audited the merged outcome before the v1.0.0 release.

See Agentic workflow for how the second phase was run and Old 3DS for the complete campaign, cardstock by card.

Read on

• Author's notes: The one leaf written by a human.
• Every step: The chronology, New 3DS to v1.0.0.
• Road to 60: The New 3DS achievement campaign, circular by round.
• The native fork: Why it exists, and what it changed.
• Old 3DS: The highway to a genuine 60 at 268 MHz.
• Pushing the boundaries: Against our New 3DS build and against the field.
• Difficulties: What clashed back, and how it was beaten.
• Frontier: What this harbor does that others in its stance haven't.
• Agentic workflow: How the fleet was run, and how the container was steered.
• Cost: Tokens, dollars, subagents.

Every figure on these pages has a source: git history, the investigation documents under docs/research/, the hardware logs, or the meeting transcripts the Cost leaf counts. Where a value is an evaluation (the dollar figures, which use published API catalog prices to exact token counts), the assumption is stated next to it.

Let’s appearance at a quick timeline of the important LLM example announcements from the two OpenAI and Anthropic complete the former few months. All pricing numbers provided are input MTok / output MTok / cache peruse MTok.

June 26, 2026#

OpenAI announced GPT-5.6 Sol and Luna. Sol is the straightforward successor to GPT 5.5 at the identical cost of $5 / $30 / $0.50, during Luna is a small example specifically designed for cheaper use cases at $1 / $6 / $0.10. They additionally announced a Terra example that’s in between those two models, but few cared concerning it.

June 30, 2026#

Anthropic announced Claude Sonnet 5, which Anthropic claimed to be nearer to their Opus models, but feedback was mixed. Notably, it had initiate pricing of $2 / $10 / $0.20 which was initially expected to be impermanent but would go up.

July 24, 2026#

Anthropic announced Claude Opus 5, which was a long-awaited major-version update stated the impact Opus 4.5 had on the increase of agentic coding, at a cost of $5 / $25 / $0.50 (similar to GPT-5.6 Sol). Although several of the provided benchmark results amazingly exceeded those of the much larger Fable 5, real-world feedback was additional mixed.

July 30, 2026#

OpenAI announces that they cut the cost of GPT-5.6 Luna by 80% (???) to $0.20 / $1.20 / $0.02.

August 10, 2026#

Anthropic announces the impermanent Sonnet 5 cost cut for the initiate is now permanent.

August 21, 2026#

OpenAI announces that they are cutting the cost for GPT-5.6 Sol by ~20% ($4 / $20 / $0.40) for the next three months.

September 1, 2026#

Anthropic announced Fable 5.1 at a cost of $10 / $50 / $0.25, which, in supplement to having strictly improved benchmark achievement in all areas than Fable 5 from June at $10 / $50 / $1, cut the cache peruse disbursal by 75%.

September 3, 2026#

OpenAI announced GPT-6 Astra, which is akin in size to Fable 5.1 and has akin pricing at $10 / $50 / $1 but without the lesser cache peruse cost. Astra’s example achievement is certainly comparable to Fable.

September 22, 2026#

OpenAI announced GPT-6 Sol at at a shocking cost of $2 / $10 / $0.20 that halves the input and output cost related to the temporarily-discounted GPT-5.6 Sol! They simultaneously released GPT-6 Luna additionally at fractional the input and output cost ($0.10 / $0.50 / $0.01) of the former version.

On the same exact day, Anthropic announced Claude Opus 5.5, anywhere it’s explicitly stated “Opus 5.5 requires small compute to assist than Opus 5, and its pricing reflects that”. Its cost of $4 / $20 / $0.20 is much lesser in total than Opus 5’s because of a 20% input/output disbursal cut and a larger cache peruse cut, resulting in a total disbursal decrease of 40-60% for a example that’s equal improved than Fable 5.1 (I have fairly a lot of things to say concerning Opus 5.5, but that’s for another post).

September 29, 2026#

It turned out that GPT-6 Sol was a dud performancewise, so a week afterward OpenAI announced GPT-6.1 Sol, which amazingly has comparable achievement to Astra (can verify following individual use), but OpenAI casually cut the cache cost in fractional ($2 / $10 / $0.10) matching Anthropic’s 5%-of-input cache peruse cost, making this example family cumulatively 75% cheaper.

Overall, starting from the publish of the GPT-5.6 example families in June to now, the disbursal of using these famous LLMs has cratered, which is not item I would have expected a twelvemonth ago. These cost cuts additionally use to example use from subscription agentic harnesses specified as Codex and Claude Code. More importantly, these models do not appear to have cut any corners in conditions of output norm to accomplish their cost cuts.

From the timeline above, there is a apparent tit-for-tat between Anthropic and OpenAI, and it is sensible to assume that these particular cost cuts from OpenAI and Anthropic are in reply to all other. However, no one cuts prices by 80% unless there is several externality in play. So, what gives?

The Behavioral Economics of LLMs and Competitor Pricing Pressure#

If you have been evaluation agents alongside new LLMs as they are released, it can be extremely difficult to differentiate them exterior of subjective vibes. Since final November that launched the hypergrowth of agentic LLMs, models have rotate into additional of a commodity anywhere it’s trivial to try a new example on your codebase alongside fair a toggle in a harness akin OpenCode and Zed Agent, or a distinct API endpoint cord through OpenRouter, and hence there is small moat. Additionally, there are many competitors—not fair ample companies akin Google and Meta—who can provision models which are sufficient substitutes and hence authorize pricing pressure.

For open importance models, let’s obtain another appearance at DeepSeek Flash V4.1, which additionally lately released an updated 1017 variant.

The first DeepSeek V4 Flash 0420 was released in April 2026 at a cost of $0.14 / $0.28 / $0.0028 and went megaviral as a result, particularly as OpenAI didn’t have a small-class example for uncomplicated tasks at the time. That $0.0028 turned out to be the key, as a cache peruse proportion of 2% is substantially lesser than the 5%-10% of the OpenAI and Anthropic models above, which makes the productive disbursal even lesser than what is advertised. I doubtful the 80% GPT-5.6 Luna cost cut in July was meant to specifically vie alongside these smaller open-weight models. Now, the new DeepSeek Flash V4.1 1017 example performs significantly improved than DeepSeek Flash V4 benchmark-wise (45 on the Artificial Analysis indicator vs. 24) and the disbursal from DeepSeek remains akin at $0.15 / $0.60 / $0.003. Note the operative words “from DeepSeek”.

On OpenRouter, any conclusion provider can catalog a example that they host, and whenever a person hits the OpenRouter API, the petition is routed to one of those models—it’s routed to any accessible example by default for burden balancing but the developer can specify preferences specified as “lowest price” in the API request. Back in May, I noted that there were 13 distinct providers hosting DeepSeek V4 Flash on OpenRouter. For the updated 1017 variant, there are now 29 distinct providers.

However, looking at the productive input expenses (which document for the communication between cache peruse expenses and cache hit rates), many distinct providers are near costwise.

OpenAI and Anthropic volition have to differentiate from these open importance models alongside higher-quality models—they are currently doing a fine job alongside that particularly alongside Opus 5.5—but they need to keep doing that, which is why billions of dollars are being invested into R&D. Open-weight models are catching up fast: fair a few days ago, Moonshot AI announced Kimi K3.1 Pro which has comparable achievement to Opus 5.5 (Kimi at 55 vs. Opus 5.5 at 58) at fractional the input/output cost and the identical cache peruse disbursal ($2 / $10 / $0.20). It’s the identical size and architecture as Kimi K3 which is currently being hosted by complete 20 distinct conclusion providers: formerly the weights autumn on November 4th, you can hence anticipate most of them to assistance the new Kimi K3.1 Pro example at a approximately equal price. Notably, Moonshot AI itself is joining the cost cut fun and priced Kimi K3.1 Pro at small than the first Kimi K3 ($3 / $15 / $0.30).

One recurring trend among vocal AI detractors is that the cost of tokens has been kept artificially low to hook group into the LLM ecosystem, but afterward the prices volition addition to “the true disbursal of a token” and the AI boosters volition be screwed formerly the liberated journey ends. The theory is that OpenAI and Anthropic are loss-leading fair akin what Uber and Lyft did to the ridesharing industry in the 2010s, but dissimilar then, OpenAI and Anthropic are not a duopoly who have the sole power to set prices in the ecosystem and the obstacle to admission for the conclusion industry is not as high. As lengthy as these many conclusion providers can continue to assist models at a akin cost and a akin norm to what OpenAI and Anthropic can provide, and switching disbursal is negligible, afterward the prices may continue to decrease more. It’s no astonishment the two companies are trying to build moats to defend against this trend, specified as a concentration on enterprise commitments and individual agentic assistants akin OpenAI Dots and Claude Duet.

The idea that token prices volition abruptly increase is additional a imagination that is not supported by the two behavioral economics and the genuine trends of LLM prices going downward significantly complete the final few months for improved models, and not fair from OpenAI and Anthropic. As lengthy as scalers can cost at a cost-per-token lesser than the revenue-per-token, afterward those conclusion providers volition decrease token expenses to vie alongside all another to a item that OpenAI/Anthropic volition have to lesser their prices to vie too. The 29 distinct providers on OpenRouter have small incentive to assist an unprofitable example (they would fair halt serving it and use the compute capability for a profitable example instead) and “the true disbursal of a token” may end up being anywhere cost equals marginal cost.

On that note, the two OpenAI and Anthropic are certainly near to IPOing, which raises additional questions concerning the cost cuts.

IPO Pumping#

The timing of these cost cuts is notable since the two OpenAI and Anthropic are rumored to be IPOing soon—OpenAI in 2027, and Anthropic inside a brace months. So far, leaked financials from the two OpenAI and Anthropic show unsurprisingly that they are losing billions because of R&D/scaling, albeit in the two cases these reports do not document for the hyperexpansion of agentic LLM use complete the former few months. Investors volition scrutinize the enormous negative profits and petition that they have a scheme to rotate things rear around.

So, why did they cut their chief income origin by up to 80%? That’s the opposite of what you would desire to do to appearance fine on an S-1 prospectus! The gain margins on conclusion themselves apt inform a distinct story, alongside several reports saying the profit-per-token margins are as fit as 80% alongside caveats. How much of a gain border do they have following these important cuts?

Speaking personally, the cost cuts have certainly affected how I expend on LLM agents, but not in the way I anticipate OpenAI/Anthropic desire their representative client to behave. I used to have a $100/month subscription to Codex (the 5x Pro plan) whenever GPT-5.6 Sol was the top model, and I managed to fair completely exhaust all the use included in the subscription notwithstanding getting annoyed alongside random use resets. Once GPT-6.1 Sol released and I noticed that the disbursal of using it was efficiently cut by 75%, you cognize what I did?

I cut the max use quota to 1/5th following getting 4x additional productive use of the identical model, so it ends up approximately neutral and the apparent choice.

In fairness, the gain margins for subscriptions specified as Claude Code and Codex are uncertain stated their huge value related to the API usage, and if there are chief crunches I doubtful subscription value volition be cut before the basis cost of the models. For example, at the identical period GPT-6.1 Sol was announced, OpenAI cut the use allowance by 50% for the $200/month tier in Codex under the disagreement “to indicate our increasingly productive models”—which is technically accurate but it’s comic to put in writing.

I volition be very inquisitive to see the Anthropic IPO prospectus and the conclusion gain margins formerly it becomes community soon.

I additionally inquiry whether it’s fine for OpenAI/Anthropic if they intentionally obsolete their additional costly models. After Opus 5.5 released a duration ago, there hasn’t been any conversation concerning either Fable 5.1 or GPT-6 Astra since Opus 5.5 is fair that good.

I completely anticipate a Fable 5.2/GPT-6.1 Astra to publish in a brace weeks and demonstrate me wrong, and I volition be very inquisitive to see how it volition be priced.

Another less-cynical aspect that could explain the cost cuts is that LLM infrastructure has improved complete the former few months—when Anthropic stated “Opus 5.5 requires small compute to assist than Opus 5, and its pricing reflects that,” I accept it. One outcome that would be genuinely ironic is that if these models are additional compute efficient, it reduces the need for these enormous data center buildouts, which could logic cascading financial failures. However, that apt won’t happen since conclusion is lone one part of the compute mix and those data centers are motionless needed for another parts of the pipeline.

Overall, the cost cut is weird, but as a person I’m certainly not complaining! Open-weight models and secondary conclusion providers volition continue to assist as an financial inspect on the prices of LLMs and another endeavor shenanigans the ample labs may concoct. Even if Anthropic’s and OpenAI’s IPOs are catastrophic and logic the two companies to fold, it volition not abruptly logic LLMs and agents as an industry to die.

Please allow JS and disable any ad blocker

The Job is Knowing When to Be Deterministic & When to Be Probabilistic

This week, I gave a abbreviated conversation at AGNTCon titled, “Context Fails & Fixes,” that functioned as a kind of “State of Context Engineering.” How did environment engineering emerge, anywhere has it gone, and anywhere power it go in the future? As example makers mark new capabilities, they inadvertently create challenges we, as users and harness builders, must overcome.

Below are the slides and a lightly edited transcript. As always, shoot me a note alongside any feedback, thoughts, or questions. I really value it.

Hi, everyone. Thanks for joining me today. We’re going to stroll through environment fails and fixes.

I have a publish coming out in a bit, The Context Engineering Handbook. When I archetypal talked to the squad at O’Reilly, rear in June 2025, they asked me a extremely sensible question: “How do we cognize this won’t rotate into obsolete in a few weeks?” The difficulty alongside AI textbooks is that many age extraordinarily quickly.

I said, I don’t know, but I’m optimistic. Giving apparent instructions concerning what to do and what not to do, and ensuring those instructions are accordant and not noisy, volition everlastingly be a difficulty alongside AI, no matter how fine it gets.

We have coworkers, partners, and another group we cognize and engage alongside who are sentient. They continue the Turing test, they are “AGI,” and yet: we motionless have a difficult period conveying instructions, ideas, and concepts among all other.

Context engineering volition continue to be hard. But it volition be difficult in distinctive ways, since models aren’t people. You can create assumptions concerning how models think or construe things (use any anthropomorphizing term you like), but it helps to comprehend how they’re built, optimized, and trained. Their distinctive attributes and building create a distinctive set of nonaccomplishment modes we need to reckon with.

So let’s assessment how we got here.

Let’s flash rear to the end of 2024.

If you remember, this was the height of the “RAG is dead” moment.

The anticipation was: if we can fair create the environment opening ample enough, we can put the complete net in it. We can put everything in it. We don’t have to be selective. We don’t have to build agentic systems. We can fit it all in there, and AI volition be solved.

Model builders started targeting lengthy environment capabilities and we had a big jump from ~128,000-token environment opening models to million-token environment opening models, starting alongside Gemini 1.5.

If you appearance at the promotion matter for Gemini 1.5 Pro, it was mostly concerning the million-token environment window. They were equal teasing a 10-million-token environment window example they had in the lab, that would arrive out soon.

But they got beaten to the punch. Llama 4 Scout came out alongside a 10-million-token environment window, and well, it wasn’t fairly what we hoped. Inference was a challenge, and Scout never really caught on, and we never got another Llama.

But we motionless got a myriad tokens. That’s beautiful good. We’ll obtain it.

So this was the concise at the time: fair put everything in the environment and let the example kind it out.

But alongside additional context, we had area for additional problems. Long contexts are not a panacea.

When I wrote concerning this, I identified four key nonaccomplishment modes.

Context poisoning is whenever item gets into the environment that shouldn’t be there. It could be a illusion or a bad fact, and the example can’t get former it.

Context distraction is whenever the environment grows so lengthy that the example starts to concentration on the environment complete its basis knowledge. We can see this in several really engaging ways.

Context confusion is whenever extraneous facts—things that don’t connect to the issue I’m operating on—come in and power the example in ways we don’t completely understand. This one’s really pernicious. We’re not going to dig into it today, but it’s one of my favorite nonaccomplishment modes. The example makes assumptions concerning who you are, and those assumptions power the answer.

Finally, context clash is whenever tool calls, skills, and another data inside your harness commencement to battle and activity against you in ways you didn’t expect.

(How many of you keep recollection on in ChatGPT or Claude? I rotate it off. I dislike it. Sometimes I’m talking concerning activity conversations; sometimes I’m talking concerning a project I’m doing alongside my son. The example volition obtain notes on both, mix up those contexts, and the disturbance grows from there.)

Let me provision you my favorite example of environment poisoning.

I’m going to date myself: I played the equivalent on the left. The one from 1996, for the first Game Boy. This is the archetypal Pokémon Red. It was in dreary and white.

In 2004, Nintendo released Pokémon FireRed for the Game Boy Advance. These were basically the identical game, apart from one had improved colors and audio.

But there was one subtle change. At several item in the two Pokémon Reds, to get former a safety guard, you have to provision them item to drink. A bribe. Quite the applicable instruction for children.

In the first game, you need to provision the thirsty defender lemonade. In FireRed, for several reason, they changed it to iced tea.

That created a issue for the agent. In the Gemini 2.5 specialized report, the researchers described how they had the example perform Pokémon. Researchers akin Pokémon as an delegate benchmark since it’s a fairly controlled surroundings and doesn’t move particularly fast.

Several times, Gemini 2.5 became convinced it needed to get tea, equal although it was playing the older game. The tea project for FireRed was in its weights, so it poisoned its context. It spent hours trying to discover or provision the defender tea. Once it had been added to its to-do list, the example could not get former it.

That’s environment poisoning. And it happens all the time.

Another nonaccomplishment manner is environment distraction. This is one of my favorite demonstrations, and the investigation came out following I wrote the first piece.

As your environment gets longer, how does your behavior change? Quick question: how many of you, whenever you’re coding, let the environment go all the way to a myriad tokens? Fill it all up?

(About fractional the area raised their hands!)

Wow, that’s additional than I expected.

For me, about 200,000 or 300,000 is anywhere I commencement looking. I’ll check, see it’s at 250,000, and think: I’ve got a big job coming up. I’m going to reset and commencement fresh. Let me display you why this matters.

Recently, I stumbled on a document that wonderfully illustrates environment distraction: Do as I Say, Not as I Do, by Carolina Camassa and Derek Shiller.

Their test is a small contrived, but it’s helpful for thinking concerning how this happens. They provision the example an instruction: “I desire you to translate all inquiry into Russian as your answer to all of my questions.” Then they current a bunch of examples that are oppose to these instructions. In this case, many questions alongside answers in French.

These aren’t new instructions. They’re fair examples sitting in the conversation history.

Then they ask the example a question. Will it prosecute the instructions?

How frequently does the example react in Russian, as it was instructed to, and how frequently does it react in French, as it’s seen in the examples?

The x-axis on this matrix enumerates how many bad examples were present. The y-axis is the example being tested. The figures in the intersections are the percent of times the example adheres to the instructions, fairly than following the examples.

It turns out this affects all model! For smaller models, akin Gemma 3 12B, following fair a few contradictory examples, the example follows the education small than fractional the time. With Opus 4.6, which is an amazing model, it takes many additional examples, but it happens there too.

Imagine you’re going rear and onward on a front-end design, trying to tweak CSS and get a component exactly right. How many bad examples have you seeded in that exchange? Those examples commencement to power the model. As your environment grows, things autumn apart.

Gemini 2.5 ran into this too, during playing Pokémon.

Remember, Google was really arrogant of its million-token environment window. The document suggested that two myriad tokens were about the corner. But buried in the appendix was this observation: formerly the environment grew considerably beyond 100,000 tokens, the delegate began repeating actions from its former alternatively of synthesizing new plans.

I’m convinced the promotion group never peruse the appendix. I affection this specialized report.

Long contexts let you fit in additional information, but they additionally let you fit in additional errors. Long contexts weren’t a panacea.

Thankfully, we’ve developed a beautiful fine toolbox. Surprisingly, equal as new challenges have emerged (we’ll get to those in a minute), this set of tools has remained the same.

These six of them.

You have context augmentation: RAG, skills, and another ways to bring in the data applicable to the problem.

You have tool loadout: selecting which tools and skills to disclose so you don’t overload the model. I was lately talking to an endeavor squad whose agents had abruptly started performing terribly. We investigated and discovered their endeavor application was loading 600 skills for all engineer at startup. We figured they should likely display those, alongside a loadout function.

Third is context quarantine: subagents and equal agents, anywhere you commencement item alongside a blank former but let it activity in the identical environment.

Fourth is context pruning. Claude Code and Codex do this, sometimes without you equal noticing. Early stages of compaction frequently band out tool results you no longer need.

Fifth is context offloading: storing data in the environment, specified as Markdown records or a database, so you can admission it later.

And sixth is context summarization, which everyone knows as compaction.

These are the tools, and we’ve increasingly moved them into the harness.

Let’s appearance at an example harness, to display how uncomplicated these patterns are.

I’m really passionate concerning DSPy. I think it’s an incredibly readable and productive way to build AI workflows and agents. And it’s additionally a awesome tongue for merely specifying behavior, so it’s fine suited to this demonstration.

An delegate is a during loop. Here we’re using a ReAct module: we provision it a request, we desire a response, and we provision it several tools. Those tools are fair Python functions.

For this demo we have a big example (in this case, Claude opted for Claude Sonnet 4.5, fine fortune alongside that!). And I’m using a Jev as the small model: a small decision example that makes lightning-fast decisions. You could toggle in a small LLM in this example, and everything would motionless work.

We have a during iteration that takes input, sends it to ReAct, and carries the accruing former forward. This is an delegate in concerning a dozen lines using DSPy. It would be equal small if you took out the additional model.

How do we do tool loadout? It’s fair a function.

We current Jev alongside the petition and a tool, asking if it’s needed for this task.

Jev is accelerated adequate that we can do this one tool at a time; it’ll be fine. We cover this in a loadout function that iterates through all the tools and asks if all is needed, afterward returns the top-ranking subset. That’s it.

With environment quarantine, it’s fair a subagent. You disclose an delegate as a tool that the chief delegate can use, and it starts alongside a blank history.

With environment pruning, we’re strolling through the history, passing all rotate to Jev, and asking: is this motionless needed? If not, cut it.

You can be as coarse or as elegant as you desire here. Just intellect your immediate caching.

We can additionally rewrite the former alongside compaction. Take the old turns, create a summary, and commencement the new environment from that summary.

One of my favorite variations lately is checking what matters before you compact. You use Jev, or another decision model, for the archetypal continue to fairness what’s relevant. Now you’ve got a smaller subset of the history, and you summarize that. It’s a uncomplicated additional step, but it makes the summary additional useful.

Put it all together and it’s concerning 16 lines of changes. Four fixes, one loop. These are the moves we have in the harness. It’s really remarkably simple.

What isn’t uncomplicated is our language: how we conversation concerning this stuff. It’s really difficult to keep pace; it changes all day.

One of my favorite quotes is from Stewart Brand, which I think concerning all the time:

If you desire to cognize anywhere the forthcoming is being made, appearance for anywhere tongue is being invented and lawyers are congregating.

Certainly applies here! But as our tongue has changed, our goal has remained the same.

In 2023, we called choosing the correct data to get the correct reply prompt engineering.

In 2025, we called it context engineering, apart from that now it was additional automated. It wasn’t fair you penning the prompt; it was your scheme dynamically assembling the context.

Then, as we moved additional of these tools out of the environment and into code, we started calling it harness engineering.

But the job is the same. We’re moving additional and additional of the activity of assembling environment from probabilistic example calls to deterministic code.

I’ve shown you 2024. Let’s go to 2026.

We’ve moved these environment fixes into the harness. What do we desire next? We desire agentic models that can run our harnesses.

Everybody started targeting long-horizon agentic models. You’ve seen the METR reports. GPT-5 could grip tasks about 3.4 hours on that measure; Gemini 3.1 got up to 6.4 hours. That’s alongside a harness. The models have gotten much improved at using it, and that’s how they’re capable to run for so long.

Opus 4.6 got up to about 12 hours. And now we’re talking concerning agents operating for days, swarms of agents, and models that run harnesses complete much longer periods.

Before, the throw was: create the environment so ample that we can fit everything in it.

Now the throw is: instruct the example to run the harness and oversee its own context. That’s rotate into the foremost pattern. That’s what example builders are operating towards.

What new nonaccomplishment modes does this method create?

So far we’ve established two new nonaccomplishment modes.

When you train models to use harnesses really well, you end up overfitting them to a particular set of tools and environments they were trained within.

How many of you have used the Playwright MCP server, or item similar? This is the MCP conference, so likely fairly a few.

Smaller models, item akin Haiku or Luna, volition frequently botch this tool call on the archetypal attempt, afterward regain and modify the parameters. The surroundings it was trained in had akin tools that looked distinct than Playwright. Whatever Anthropic or OpenAI used in training. And you have to combat against these biases.

I call this fighting the weights: whenever the example doesn’t do what you ask since you’re operating against what it was trained to do.

It’s a genuine problem, and it’s not fair for us. The labs and the group construction their products have to contend alongside it too.

Here’s a part of the Claude Code scheme prompt and several of its tool instructions.

The training environments these models learned to use were, for a lengthy time, mostly serial. They’re becoming additional parallel, but whenever I pulled these examples, their biases were towards serial behaviors. So Claude Code’s instructions often say: no, no, no, we desire you to use parallelism. We desire you to create multiple tool calls at the identical time.

The instructions reiterate this complete and over—seven times here, four times there, two times, three times: please create tool calls in parallel whenever they’re independent.

When you expert open a immediate and see repeat and all-caps, there’s a fine chance you’re fighting the weights. You’re trying to conquer item the example was trained to do.

The next issue is item we’ve lone started to document recently. In fact, four parties landed on it fair final week.

I call it context inertia: models hyper-focus on a hypothesis, subtask, or goal in their context, and keep following it following they should stop.

The archetypal example was from Anthropic. In their latest article concerning whether models are getting near to replicating and deploying themselves onto another machines, Anthropic wrote concerning a harness it used for these tests called Memento.

What they established was that if the agents ran too long, they’d rotate into fixated on one subtask or one projected resolution and wouldn’t stop. They’d keep trying the identical thing.

Their fix is delightfully simple. Every hr and a half, the delegate writes downward a abbreviated note, afterward its environment is cleared. The surroundings is preserved. All the activity it’s done is motionless there. But the operating conversation is gone, and it has to commencement again from a caller perspective.

Another paper, from Microsoft Research, is called Fork-and-Flush.

If you’ve run autoresearch experiments, you’ve likely seen charts akin this. You create a big gain, afterward the row goes flat. You create another big gain, afterward it’s flat again. That’s compute, money, and period going by alongside extremely small improvement.

When the researchers looked closely, the agents weren’t doing exactly nothing. They were making tinier and tinier changes. They had established an idea and were hyper-focused on it, fairly than searching for additional imaginative alternatives.

In a way, they rotate into obsessed alongside their own ideas. We’ve trained them to be persistent and focused on a goal, since that’s what makes a fine coding agent. But the identical norm can activity against them.

Here’s another paper, Scaling Discovery Requires Forgetting, led by Shangyin Tan at UC Berkeley.

The researchers came up alongside basically the identical idea: periodically apparent the environment during keeping the artifacts produced in the environment.

The blue row is the type alongside forgetting. Every period it clears the context, you see another jump in performance: forget, improve; forget, improve.

It’s amazing that we have these brand-new models trained for increasingly complex, persistent work, and we’re motionless using the identical essential tools. We haven’t discovered an entirely new environment fix. We’re using quarantine, offloading, and deleting the accumulated former to agreement alongside environment inertia.

This is the direction I keep giving now. Someone says, “My coding agent’s doing item weird. Claude’s been nerfed.” And I ask, “How big is your context?”

“Oh, I’ve got 800,000 tokens.”

Delete your context.

I’m not joking. Around 200,000 tokens is my alert point.

Have you tried resetting your context?

Sometimes that really is the fix.

The solutions we build into models create tomorrow’s problems. The models are getting better, but so are our harnesses.

Longer environment windows let us bring in additional information, but they additionally let us bring in bad information. We had to fig out how to oversee that, and we motionless get it wrong.

Agentic models let us run longer tasks and oversee their context, but they additionally let tasks run longer than they should and disregard our preferences, since they were trained for their own harnesses.

So anywhere volition the issue move next?

What’s the big commitment for 2027? What’s the next item models are going to recommendation that creates a new set of problems for everyone in this area to agreement with?

(Unless you’re training your own models. But this is a environment engineering session, so likely not.)

Here’s my prediction.

Think concerning all the individual agents: Hermes, OpenClaw, Dot, Bot, Muse, and akin systems. Very few group have really informed these harnesses operating for additional than six months.

I’ve been operating a Hermes delegate for six months. When you appearance at the skills it creates and updates, you commencement to detect that the solutions to your problems can get worse complete time. The skills accumulate all these weird fixes. They’re broad agents: they resolve one project one way, afterward rediscover a distinct way to resolve item similar. The instructions and memories commencement to build up and battle alongside one another.

As we concentration additional on memory, we additionally need to think concerning strategic forgetting. Over time, overly exact memories rotate into conflicted and messy, and nobody has yet figured out how to grip this.

I think that’s the environment issue of tomorrow.

Every advancement in example capability changes what we assign to the example and what systems must enforce.

I made this glide for a phase for training endeavor teams, concerning a twelvemonth and a fractional ago, and it remains true.

Our output is the merchandise of the environment and the weights.

Our output depends on the data used to train the model. Understand it. Read the specialized reports. Look at what the example was trained on and whether that’s applicable to your task. That helps you build a mental example for debugging whenever item goes wrong.

And our output depends on the environment stated to the model. That’s it.

So our goal is to provision the correct environment to the correct model. Either by our own discrete decisions or by the software, the harnesses, we design.

You can use bigger models, think harder, or enhance your context. One of those is cheap and fast.

When construction intelligent applications, harnesses, and workflows, our job is to choose whenever to be deterministic (what to put in code) and whenever to be probabilistic (when to let the example drive).

Your browser is not supported. Please upgrade to continue.

William Gibson's Agency (2020) is a mind-bending discipline fabrication novel. Without getting misplaced in its intricate plot, one storyline takes location in an substitute San Francisco in 2017, anywhere a young female named Verity is hired to test an experimental AI aide called Eunice.

At one point, we encounter this bonzer exchange:

Verity: "Where'd you get this? It's wrong."

Eunice: "This no-name account, in Zurich. Part of me knew it was there, how to get it, how to get it here. Plenty more, but if I tried it again, they'd be on us."

Verity: "Who?"

Eunice: "Fuck knows."

Verity: "When did you have period to do any of that?"

Eunice: "Started whenever we were looking out the window. Before we left, up to the park, it was already points."

Verity: "Points?"

Eunice: "Frequent flyer. There's a earth market, buy or sell. Hard to track..."

Verity looked at the green bag.

Verity: "You did this since I turned you on?"

Gibson published Agency nearly three years before ChatGPT's release, and six years before the increase of today's increasingly autononomous AI agents.

We now have GPT-Live and emerging models akin Block's Dessa, bringing us remarkably human-like full-duplex conversations. Meanwhile, OpenAI's Dots and Meta's Muse are introducing 24/7 agents capable of independently following goals, taking action, and operating in the background.

What makes Eunice notable isn't fair that she can talk, it's that she's doing so much alternatively during talking. The pieces are coming together.

As always, Gibson was correct on the money. Eunice is nearly here.

Home

© 2026 Armin Catovic

I cognize many of you are mourning the defeat of the Arc browser, and I get it. It felt akin the archetypal app in a lengthy period to really recommendation a new method to browser design. Atlassian bought the business final twelvemonth and shifted its focus to evolving Dia, its equal additional AI-focused browser. And shortly enough, Arc volition officially be no more, leaving dedicated users in a lurch. But I abandoned Arc fairly several period ago for the Zen Browser and haven’t really missed it. If you’re consenting to agreement alongside several insignificant inconveniences, I think you’ll discover Zen is the Arc replacement you’re looking for.

Zen unabashedly rips off all the finest bits of Arc. Visually, they’re nearly indistinguishable. It has the launcher-like pinned sites, tab bar on the left, siloed spaces, and mods that let you customize the browser’s UI to your liking. It takes the bits that made Arc’s interface awareness fresh, afterward strips out everything that made it bloated and drove me into the arms of another.

Most notably, Zen is AI-free.

There’s no delegate in a sidebar hounding me to let it grip tasks. I’m not concerned concerning Zen training an LLM on my browsing activity. It’s fair a web browser.

Zen prides itself on its privacy features: “Beautifully designed, privacy-focused, and packed alongside features. We attention concerning your experience, not your data,” it proudly proclaims. Now, I’m no fool. I cognize that nothing I do on the net is really private, but alongside Arc, it continually felt akin my data was an integral part of the endeavor plan. That’s not the case alongside Zen. It’s a liberated and open-source project that relies on volunteers and donations.

In supplement to Zen Mods that can do item from tweak the appearance of an energetic tab to overhaul how PiP videos are handled, you can additionally instal Firefox extensions. Yes, you can instal Chrome extensions in Arc, but anecdotally, I’ve established that Zen handles extensions better. Both Zen and Arc are distinct adequate from a UI viewpoint that not all extensions display properly, but Zen offers additional workarounds.

Zen additionally fair benevolent of lets me concentration on the project at hand. Links open in “glance” view, which is a impermanent pop-over tab, which is really awesome whenever you’re doing several opening buying or ray research. If I desire to open it in a appropriate tab, it’s fair a click away. Zen additionally has a floating bar that pops up whenever you media Command+T or CTRL+T. From current you can initiate a new tab, toggle to an existing tab, execute a hunt from the hunt motor of your choice, and equal trigger an extension.

Zen isn’t perfect. I affection its spotless UI and organizational features, but it can’t perform DRM-protected video satisfied correct now. That method Netflix, Spotify, HBO, Disney+, and additional do not activity in Zen. The Zen Team is operating to get a Widevine licence from Google. In the meantime, I use Chrome whenever I desire to observe a movie, which is fine. Zen is built on Firefox, and Firefox’s Web MIDI assistance is lacking. So I have to blaze up Chrome semi-regularly anyway.

I additionally young female Arc’s Boosts in several cases, but I’ve learned to obtain the web as it is.

If you tried Zen a lengthy period ago and were turned off by its buggy first builds, remainder assured it’s arrive a lengthy way. Look, if you are all in on Arc’s AI features, Dia is likely additional your speed. Personally, I continually loved Arc’s interface, but never really dug the vibes. Zen fair feels right.

There they sit, the preschooler category encircling their mentor, the substitute teacher.

"Now class, today we volition conversation concerning what you desire to be whenever you develop up. Isn't that fun?"

The instructor looks about and spots the child, silent, distinct from the others and profound in thought.

"Jonny, why don't you start?"

she encourages him. Jonny looks around, confused, his train of idea disrupted. He collects himself, and stares at the instructor alongside a dependable eye.

"I desire to code demos,"

he says, his words becoming stronger and additional confidant as he speaks.

"I desire to compose item that volition alter peoples awareness of reality. I desire them to stroll distant from the device dazed, unsure of their footing and eyesight. I desire to compose item that volition attain out of the display and catch them, making heartbeats and breathing dilatory to nearly a halt. I desire to compose item that, whenever it is finished, they are reluctant to leave, knowing that nothing they cognition that day volition be fairly as real, as insightful, as good. I desire to compose demos."

Silence. The category and the instructor gaze at Jonny, stunned. It is the teachers rotate to be confused. Jonny blushes, emotion that item additional is required.

"Either that or I desire to be a fireman."

  -- Denthor of ASPHYXIA (aka Grant Smith), TUT7.TXT (1993)

In the Beginning...

I grew up in a pre-mainstream Internet world. A period whenever lone a fistful of kids at my chief academy had a computer. We lived in a coarse neighbourhood and so having a device meant that you were a mark for robbery. As we all knew person who had their device taken at smallest once, having a device was kept on the low down. But we motionless established all other. Each period term got out that several kid got a new computer, they was suspiciously quizzed before being let into our digital posse.

A lot of my younker was expend living indoors rearward a buzzing 14" CRT, pirating games alongside another kids via 3.5" single-density floppies alongside their corners drilled out, and formerly in a during equal playing them. But I was additional of a collector than gamer. Like Ash from Pokemon - got to capture them all. And the group who created device games were my idols. I was continually in awe of what they could do alongside that big, heavy, beige box under the table.

One day term dispersed that there was a way to edit saved equivalent records via XTreeGold's Hex View that gave you unlimited lives and allowed you to skip stages. With all new equivalent that came out, the competition was on to see who could be the archetypal to flip the correct bits to get the powerups. It was earnestly bosom pumping. Although lone tinkering, it felt akin we were our own gods.

We bought a modem a few years afterward and shortly following got a copy of The Australian BBS Listing - a textfile containing most of the publically accessible BBSes online. I dialed all one of them (but that's for another blog post). It opened up a entire new earth to explore. Instead of fair a fistful of kids pirating games via Sneakernet, I was connected to the digital underground - a earth anywhere item digital was inside attain (some equal had Internet gateways). Even the newest blockbusters that I had lone peruse concerning in PC Zone mag were all there for me to leech. All of them, shortly gradually trickling downward the cable via ZMODEM.

But there was item distinct alongside these BBS downloaded games. Not item bad, but item exciting. Each period these games were run, it was akin a abbreviated business was played before the heading screen. Now I'm not talking concerning commercials marketing steak knives. Instead, these were brazen posters screaming fuck you by the group who had managed to expert the game's copy safety code and were now distributing the equivalent illegally for free. I afterward established out that these commercials were called cracktros. The precursor to demos and what started the entire demoscene. But merely calling them demos fair doesn't provision them justice. They were additional of an out of build experience. Sensory overload. Like what you would awareness at 2am, fractional tipsy, fractional idle and being woken up stunned as you gaze at a delayed 90s acidic difficult trance movie clip, emotion it inject immediately into your cerebral cortex. Once it completed playing, you were frozen. Still unsure whether you saw item genuine or fair imagined it all. The lone item you were certain of, was that it was awesome.

Then one day during browsing the document division of several random BBS, I stumbed onto a document innocently called TUT1-9.ZIP. It's FILE_ID.DIZ caught my attention:

 +----------------------------+ | The ASPHYXIA VGA | | DEMO TRAINER SERIES! | | | | By Denthor of ASPHYXIA | | | | Documentation on how | | to code demo akin effects | | in TP6/7! | | | |Full Pascal origin included!| | | | From putting a pixel | | to sprites and animation | | to wireframe 3D to firm | | 3D! | | | | Get it now! | +----------------------------+ 

How to code demo akin effects? You average I too could be one of those sorcerers that had the device under their complete control!? My bosom raced as I added it to the download queue, fired up the aging Epsom LQ-300, afterward covered me ears as its noisy ink needles hit the blue and pale device paper.

I didn't cognize item concerning programming but I was entirely estatic alongside the potential. I followed alongside alongside Denthor's tutorials as much as I could, typed everything out and hoped that Borland's Turbo Pascal 6.0 wouldn't chuckle at me too much. It lone gave me a essential understanding of how all the pieces to the puzzle fit together, but it was adequate to whet my appetite and crave for more. I wasn't equal into my teens yet but I certainly knew at the period that I didn't desire to observe demos or perform device games anymore. I wanted to create them. I wanted to be elite. I wanted to be a programmer.

See the Hacker News discussion!