Active development · Power-user workspace
FRIDAY
The assistant I wanted to use.
FRIDAY is the personal operator I would build for someone like me: someone who wants access to the models, memory, tools, and machinery behind the interface.
The ambition is a deeply integrated assistant that can participate in real work. That means moving between conversation and execution, keeping useful context, and bringing different tools into the same workspace. It also means letting the person using it understand what is happening.
Those ambitions create practical engineering problems. Which model should handle a request? What happens when a specialist route is unavailable? When should an action need confirmation? How does an optional service fail without making the whole interaction misleading?
FRIDAY is where I work through those questions in a hands-on system. Its interface exposes more of the controls because visibility is part of the product: routing, execution, memory, and failures all affect whether an operator can be trusted.
It remains an ambitious, evolving workspace. The lessons it produces also inform LAILA NEXT, while FRIDAY retains its own purpose as the version built for a power user who wants the whole machine available.
When a route cannot finish
The current chat path can send coding work to an optional specialist and fall back to the primary model. Transport errors remain distinguishable from assistant replies, so a missing service need not look like an answer.
Tool execution has trust and confirmation gates. Memory uses a provider boundary with fallback behavior; neither a model reply nor an optional memory service owns permission to execute tools.
SketchMath is an interface experiment within the workspace. Its documented deployment uses the legacy selection path; advanced document and CAD feature paths remain gated. These experiments inform LAILA NEXT, which has an independent runtime.