253 karma · joined November 6, 2023
Essays on agent architecture, evaluation, and intelligent organizations: arizenai.com
Production-Ready AI Agents Book (2025): amazon.com/dp/B0G43PPDSP
Contacts: github.com/arizen-dev bobriakov.igor [at] gmail
I tested Gemini CLI while ago, and it was awful tbh.
So there is also a question, what would be happening to these.
And cost of acquiring learning via users feedback versus additional learning data value for a given company will dictate whether such company will give up or will continue subsidized usage, despite being unprofitable on the paper, but probably really valuable as a long term strategy for GTM and product development and increased learning rates.
As, if there are no constraints in some specific area, there is no kinda "survival need" to improve there, hence brain is not working as hard/smart/deep as it could.
This one is really promising, as it may allow to close major gap with Claude in design/UI skills
For most important work (complex, cross-domain inquiries etc.), I still rely on Codex GPT 5.5 though.
It felt, like Fable was able to kinda grasp very deep knowledge/intelligence layers and outline solution not only in agreeable way, but rather it proposed to prioritize solution items, with discarding some of the items, which made a lot of sense to me.
While Fusion felt more like a bit diversified answer of the same class of pre-Fable SOTA models, without touching the depth of knowledge/intelligence layers, which Fable was able to get, in my very limited tests I did, while Fable was accessible.
I ended up using DeepSeek V4 Flash as main workload model, while keeping DeepSeek V4 Pro and Qwen 3.7 Plus as advisors on system architecture and other advanced matters to guide DS Flash.
I run a simple benchmark on OpenCode Go models while ago, if anyone want to read more: https://arizenai.com/seven-models-judged-each-other/
Pursuing a meaningful goal almost always requires enduring unpleasant phases and friction along the way.
-Isaac Newton
I wanted to share a reference implementation I architected for moving AI Agents from local prototypes to production services.
The Context:
It is relatively easy to get an agent working on a local machine where you can watch the terminal output and restart it if it gets stuck. However, the architecture often breaks down when moving to a headless, hosted environment where the agent needs to handle loops, persistent state, and structured output failures autonomously.
The Solution:
This repo is a 10-lesson lab where you build an "AI Codebase Analyst" designed to handle those operational constraints.
Key Architectural Decisions:
1) State Management (LangGraph): We use LangGraph to implement the State Machine pattern rather than a linear Chain. This provides a standardized way to handle cyclic logic (loops) and persistence without writing "spaghetti code" while loops.
2) Reliability (Pydantic): Treating the LLM as a probabilistic component. We wrap tool calls in strict Pydantic schemas to catch and retry malformed JSON before it hits the application logic.
3) Deployment (Docker): A production-ready Dockerfile setup for serverless environments.
The Repo Structure:
starter branch: A clean boilerplate to build from scratch.
main branch: The full solution code.
curriculum/ folder: The step-by-step guide.
Happy to answer questions about the stack or the trade-offs involved.