Iris Factory

Agent Framework

The agent layer that lets Iris act, not just answer: small modules for the clock, terminal, apps, music and calendar, picked per request, with agents generated on demand as the longer-term goal.

+Scored routing — The best-fitting agent handles each request
+Seven agents — Clock, terminal, apps, music, calendar, memory, code
+On-demand agents — Generated as needed, planned

ask for early access ↗€9/yr or €19 once

What it is

Factory is the agent layer: small modules that act on a request. Every agent scores how well a request fits it, and the highest score above a threshold runs, so a question about the time goes to the clock agent and "play something" to the music agent. The agent's result goes back to the language model, which always phrases the answer, so every reply sounds like Iris rather than raw tool output. If no agent is confident enough, the model answers on its own.

Agents today

Clock, terminal, apps, music, calendar, memory and an early code agent. The apps, music and calendar agents are macOS-specific for now; how they should work on other platforms is still an open decision.

Where it's going

The planner, OS and git agents come next, along with a finished code agent. Longer term, the aim is agents created as needed rather than all shipped up front, with third-party agents running under capability-based permissions in a sandbox.

Status

[x]Agent router
[x]Seven built-in agents, three of them macOS-only
[ ]Planner, OS and git agents; a finished code agent
[ ]Agents generated on demand
[ ]Third-party agents with capability permissions and sandboxing

cd .. all of nf iris suite