miatz™
Verify a credentialLog inSit ChuunSit Chuun
  • Learners
  • Mentors
  • Business
CoursesApplied AIProgramResidencyPlaygroundsWar RoomsXookAtlasReadiness Check
miatz

The AI-era engineering institute. The machines got fast — we train the drivers. Real work, a daily loop that compounds, and a record that proves you can think.

Toggle theme
Explore
  • Courses
  • Applied AI
  • Program
  • Residency
  • Playgrounds
  • War Rooms
  • Xook
  • Atlas
  • Readiness Check
  • Tokenizer Lab
  • Chunking Lab
  • Prompt Anatomy
  • Calibration Lab
  • All playgrounds →
Learn
  • Courses
  • The Method
  • The Residency
  • Chuun · Entrance Examination
  • Manifesto
  • The Itz'at credential
  • Verified engineers
  • Playground Catalog
  • AI Use-Case Atlas
  • AI Readiness Check
  • Guides
  • Glossary
  • Compare approaches
  • Blog
  • What's New
For teams
  • For Students
  • For Mentors
  • For Business
  • Classroom migration
  • Miatz Index
  • API reference
  • Sit Chuun
  • Log in
Company
  • About
  • Experts
  • Why it's free
  • Pricing
  • FAQ
  • Contact
  • Privacy Policy
  • Terms of Service
  • Your data & privacy requests
  • Grievance redressal
  • Security & disclosure
  • Subprocessors
  • Data Processing Agreement
Take miatz with you

The Android app is live. iOS is on the way.

Available on AndroidGet it on Google Play
Not yet on iPhoneiOS — use the web app

Miatz Private Limited

Registered office:
C-101, Lotus Tower, Arge Urban Bloom, 30/A, 4th Main, 2nd Stage, Yeswanthpur, Bengaluru, Karnataka 560022, India
CIN:
U62013KA2026PTC226418
GSTIN:
29AAVCM3922D1Z6
Phone:
+91 82802 73456
Email:
hello@miatz.com
Website:
miatz.com
Grievance Officer:
Aishwarya · aishwarya@miatz.com · replies within 30 days
© 2026 miatz · Miatz Private Limited · Built in Bangalore·PrivacyTerms

miatz™, Itz'at™, Tuukul™, T'aan™, Kanan™, Xook™ and Chuun™ are trademarks of Miatz Private Limited (registrations in progress) · what the names mean

miatz
Free concept playground · no account

Context Window Lab

Bury a fact in context and watch the model forget it.

All 90 playgrounds Join the free cohort

Context Window Lab

AvailableFree

Bury one fact at a chosen depth in a long context, then watch how likely the model is to retrieve it. Recall is highest at the edges and collapses in the middle — and it thins further as the context grows and distractors pile up.

startmiddleend
37%retrievalLostNeedle: middle of context
◆The invisible window, made physicalwatch the middle go cold

The context window is normally a number on a spec sheet. Here it’s a container you fill, and the curve below is the retrieval probability at every depth for a 64K context with 8 distractors. The dip in the middle is “lost in the middle” — not a bug you can prompt away, but how attention is shaped.

0102030405060708090100

Lost · 37% recall — the middle-of-context fact is likely ignored.

Share on WhatsApp
Was this playground useful?

Context Window Lab

Hide a single fact somewhere inside a long context, then watch how likely the model is to find it again. Drag three dials — context length, needle depth, and distractors — and the lab renders a retrieval probability plus a live degradation curve across every depth. The moat is what it shows: recall is high at the edges of the window and collapses in the middle ("lost in the middle"), and it keeps thinning as you stuff more in. Instead of citing someone else's benchmark chart, you generate the curve on your own setup. Runs entirely in your browser (0 uploads, works offline).

How to use it

  1. Pick a context length (1–200K tokens) — the size of the haystack the fact is buried in.
  2. Set the needle depth: 0 = the very start, 50 = the dead middle, 100 = the very end.
  3. Add distractors — look-alike blocks that compete for the model's attention.
  4. Read the retrieval gauge (found or lost) and open the X-ray to see the U-shaped curve. Load a preset — Edge, short, Typical chat, or Buried, long — to feel the extremes.

What this clears up (the fundamentals)

  • A bigger window is not a bigger memory — attention does not spread evenly. Models attend most to the start and end of a context and least to the middle, so a fact's position decides whether it survives.
  • "Lost in the middle" is a shape, not a bug — it is how attention is distributed, not something you can prompt away. Put the fact that matters at an edge, not buried halfway down.
  • Context rot is real — as the window fills, retrieval degrades everywhere. A fact that would be used in a lean prompt gets ignored in a stuffed one, even at the same depth.
  • Distractors cost you — every look-alike block you add dilutes attention on the one that matters. More context is not free; over-stuffing is a retrieval tax.

Where it's used

A top-of-funnel AI-engineering reliability check — the fastest way to feel why "my long AI chat got dumb" is a measurable curve, not a mood. It's a miatz build-lab concept playable: play the needle-in-a-haystack here, then learn to build the retrieval model and the degradation curve yourself in AIE-103.

FAQ

What is "needle in a haystack" testing?

You place one specific fact (the needle) inside a large body of filler text (the haystack), then ask a question that requires that fact. Rerunning it at different context sizes and depths maps exactly where the model stops being able to retrieve it.

Why does the middle score worst?

Long-context attention is U-shaped: it is strongest at the beginning and end of the window and weakest in the middle. That's the "lost in the middle" effect — a fact at 50% depth is the hardest to recall, which is why the curve dips there.

Does a longer context always hurt?

At a fixed depth, yes — this lab models context rot, where retrieval thins as the window grows. In real systems a longer window can still help if it lets you place the right fact at an edge; the lesson is to spend context deliberately, not to max it out.

How is the probability calculated?

It's a deterministic teaching formula: a U-shaped depth factor (high at the edges, lowest at the middle) multiplied by a length penalty and a distractor penalty. No model is called, nothing is random — the same dials always give the same curve.

Is anything uploaded?

No. Every dial is scored entirely in your browser — nothing is transmitted, stored, or logged. Turn off your Wi-Fi and it still works.

Limits

This is a teaching model of a real effect, not a benchmark of any specific model. Actual "lost in the middle" curves vary by architecture, training, and prompt, and some models handle long context far better than others. Use the lab to build intuition for why position and size matter — then measure your real stack with your own needle-in-a-haystack runs.

Related

Part of the miatz playgrounds. Explore the rest from the playground catalog.

Bookmark this page (Ctrl+D, or ⌘D on Mac) — it works offline the next time you need it.

Try it live

  • Agent Builder

    Live

    Watch the planner-executor loop light up, node by node.

    AiBrowser (JS)Medium
    Play it now
  • AI Coding Dojo

    Live

    Watch the coding agent's plan, diffs, and blast radius live.

    AiBrowser (JS)Medium
    Play it now
  • Cost & Latency Bench

    Live

    Watch a demo's pennies turn into a production cost cliff.

    AiBrowser (JS)Medium
    Play it now
  • Evals Runner

    Live

    Where the code grader and the AI judge disagree, look closer.

    AiBrowser (JS)Medium
    Play it now
  • Fine-Tuning Forge

    Live

    Slide through cached training runs to find the tune-vs-prompt break-even.

    AiBrowser (JS)Medium
    Play it now
  • MCP Playground

    Live

    Wiretap the protocol traffic between your agent and its tools.

    AiBrowser (JS)Medium
    Play it now

Ninety playgrounds. Zero setup.

Every concept here is playable free, no account — and inside the program you learn to rebuild the machinery yourself.

Browse all playgrounds Join free