Posts
Tool results are data, not orders
Why the Geenius Chat engine reads tool results as data and never as instructions, and what that does and does not promise. Chat is not live yet.
One interface, many models: how Chat picks who answers
How Geenius Chat talks to AI providers through one interface, how a router chooses, where keys live and how the plug-ins are tested.
Why Geenius Chat has its own agent engine
Why we built our own agent engine for Geenius Chat instead of wrapping one AI provider, and what that changes for long tasks, models and safety.
A long task that survives a closed tab
How Geenius Chat saves an agent run step by step, what happens when a run is interrupted, and what a run can and cannot do yet.