Fuzzy Land

Inspired by Rethinking how we Scaffold AI Agents

Turning apps into AI systems creates fuzzy lands. When should you add fuzziness to your app?

🏛️ Fuzzy Zero

All exact land. No fuzz. Every step is set. User input is strict. Output never changes.

image

💅 Fuzzy UI

A small UI part is fuzzy land. Users type free text. Backend stays strict.

  • Pros: UI feels smart.

  • Cons: User input is wild. Output is same old, so what's the point? 🤷‍♀️

image

☑️ Fuzzy UI: Clarify

Add steps to clarify what users want. Bridge fuzzy UI and strict backend. Set clear rules up front.

  • Pros: Less confusion. Clear rules.

  • Cons: More steps for users.

image

🤖 Fuzzy API

Add a small fuzzy land to the API. For example, click to get insights.

  • Pros: Fuzz is small. Most of the app is clear. Users know what to expect.

  • Cons: Output is safe. Less wow.

image

�� Constrained Flow

Exact-led fuzziness.

  • Pros: Reliable. Good for the right job.

  • Cons: Feels like workflow or automation, not very agentic. (if it does the job, why bother?)

🎲 Fuzzy Flow

Make the whole app a fuzzy land. It may contain some exact lands but it's a fuzzy-led experience. AI runs it all.

  • Pros: If it works, it's huge. My attempts stay as fun prototypes.

  • Cons: Hard to steer. Costly. Wild.

image

📚 Appendix

My main takeaways from Rethinking how we Scaffold AI Agents:

image
image

Last updated