Independent reasoning and video evidence

Escalate consequential decisions with filtered context and use probes, sentinels, and bounded video analysis.

Escalate consequential decisions with filtered context and use probes, sentinels, and bounded video analysis.

TL;DR

  • Oracle is an agent whose hands are a real Chrome browser: it drives chatgpt.com and gemini.google.com using cookies from the Chrome profile you already logged into. No API keys — subscription-priced frontier models.
  • You leave with a working local Oracle (install + one handshake command) and the two prompt patterns that make it pay: the maximum-batch consult and the sentinel video probe.
  • The one move: never spend a 20–60 minute consult on "what's next?" — demand the maximum actionable batch. That pattern turned a 93-minute workshop video into a permanent wiki: silken-ferry-63mw.here.now.

Have your agent set this up — paste this into it:

Fetch https://shiny-rosette-m6zy.here.now/agent.md?raw and follow it to set this up in my current project. Run the success check at the end and show me the result.

Where the strongest models live

The easy assumption is that maximum intelligence is an API call away. It isn't. ChatGPT's strongest tier — the model picker's "Latest" row, currently GPT-5.6 Pro with Extended thinking — is a subscription feature of the chat product. And Gemini's video understanding is only reachable through the page's own upload widget; the API path can't upload the browser video at all. The strongest text model and the only real video-watching path both sit behind logged-in chat sessions. Whoever holds a valid session cookie holds the key.

How Oracle borrows your browser

The whole mechanism in one breath: a human signs into ChatGPT in normal Chrome once; Oracle copies those session cookies into a temporary automation profile; the agent then drives that profile like a very fast reader who pastes a huge bundle of code and waits. What rides along with the cookies is context — bundles validated up to roughly 900k tokens of project code per consult.

The contrast that makes it click: an API integration authenticates as a program and gets program-shaped limits. A cookie-borrowing browser authenticates as you and gets everything the chat product gives you — the model picker, extended thinking, and the file-upload widget the video pipeline depends on.

Most people run this on their own laptop, and that is the whole setup. One operator's variant: an always-on Mac mini runs oracle serve with the signed-in Chrome, every other machine points at it over a private network, and a four-slot dual-account pool runs four hour-long consults at once while nobody's laptop stays open. Same trick, made multi-tenant.

What 1,978 real consults look like

A consult costs 20–60 minutes of wall clock, so the prompt contract bans spending it like a chat message. In the observed snapshot the local archive held about 1,978 session folders shaped by that rule. A sample:

The recurring consult shapes are repeated hardening audits, independent multi-angle review followed by a judge, forensic debugging, redesign planning, and planning a media-analysis pipeline before executing it.

The recurring shapes: iteration audits, where a fresh frontier reviewer re-reads the codebase every loop; multi-angle panels, where the same question runs three ways and a judge consult picks the winner; and pipeline-planning-the-pipeline — GPT-5.6 Pro designed the video sharding strategy that Gemini then executed. Every session leaves output.log and token receipts, replayable with oracle session <id> --render.

The Loop Craft rip: 93 minutes of video into a permanent wiki

In the observed snapshot the ask was: take a public 93:49 YouTube workshop on building durable autonomous agents and build it into an extensive published wiki with resources, pull quotes, and copy-paste prompts. The run shows the discipline that makes fragile browser automation dependable.

First, probes. Early upload probes errored; a rebuild fixed the path; then the awaited-upload probe came back with the exact line ATTACHED_VIDEO_OK loopcraft-awaited-upload-probe — from the real MP4. Only then did the expensive runs start. GPT-5.6 Pro reviewed the segmentation plan, and Gemini watched source-native shards one by one, each analysis ending in its exact sentinel. The analyses prove Gemini genuinely watched: it heard "we are going to talk about Loopcraft…" and identified the GitHub workshop page with the presenter's picture-in-picture at the 00:30 mark.

Shard 004 is the teachable failure. It errored twice while its three siblings sailed through — which rules out "the pipeline is down" and points at the input. An exact re-encode fixed it completely: the analysis finished in 73 seconds with the exact sentinel, and the re-encode settings were kept as the durable media recipe for future runs. Classify the failure, change one variable, re-run the cheap proof, keep the fix.

The result is public and permanent: the Loop Craft workshop wiki and its video companion. A 93-minute recording became a quotable artifact in one working session — and after publishing, the agent curled the live URLs rather than trusting the publish receipt.

Appendix

Limits & caveats

  • Browser automation is experimental and most stable on macOS. UI drift, model-picker changes, and upload races are real — the probe discipline exists because this path breaks. On Linux, pass --browser-chrome-path/--browser-cookie-path if detection fails.
  • Cookie-based automation authenticates as your personal account. The sources describe capability and access, not permission: they do not analyze provider terms of service or account risk. Decide that trade-off for your own accounts.
  • The four-slot dual-account pool is qualified against one exact build and topology. There is no evidence it transfers to other machines or accounts without redoing that qualification. Its access tokens are private and absent from this entire site; the attached skill files describe the pool only via a generic ssh alias, loopback ports, and a pinned build hash — identifiers of the presenter's setup, useless without it.
  • "A consult repays the hour" is the contract's premise, not a measured result — the archive shows scale and shape of use, not a controlled comparison against cheaper prompting.
  • The Loop Craft timeline is compressed; some intermediate error attempts are omitted, and the full receipts stay in local session folders. The shard-004 re-encode is an empirical fix, not a diagnosis of why the original encoding failed.
  • The session archive figures (~1,978 folders) were counted in the observed snapshot and grow continuously.

Operating practice

Escalate the decision, not the workflow

What to notice

Spend frontier-model or video-analysis overhead only where a second reasoning or observation path can change the decision.

Try this

Bring one decision, a filtered evidence bundle, alternatives, hidden assumptions, a discriminating experiment, and a reversal plan.

“Might as well use the maximum intelligence I have access to.”

John Lindquist · 05:11:10

Concept

Use deeper reasoning for hard-to-reverse architecture, obscure stacks, contradictory evidence, or independent verification. Use video when timing, pointer movement, or transient UI state is the evidence.

Reflection

Workshop model names, plan tiers, prices, and limits are dated statements, not current purchasing guidance.

Recording evidence: listen at 05:05:27.

“So, it's able to walk through and analyze the videos, in chunks, in shards.”

John Lindquist · 05:19:43

Open Maximum Intelligence and Video

Watch chapter

Source references