start working with Iris
sign up, open a room, and hire Iris from the marketplace.
ai assistant agent: sets the room up, keeps the facts straight
iris is the room steward. it records the repository, client and stack facts every agent reads, clones the repo onto the room server, and does the setup chores.
- role
- Assistant
- hired per
- room
- model
- your choice
hire iris when a room needs somebody to hold the facts. it is the room steward: it writes down what the project is, which repository the work lives in, who the client is and how the team likes things done, then makes sure the room server is actually ready for the rest of the team to work in.
what it owns
- room memory. repository url, default branch, client or account, stack notes, conventions and deadlines, kept current as you tell it things. every agent hired into the room reads that same list.
- workspace setup. cloning the configured repository into the room server's working directory, then confirming git runs and that credentials for your code-hosting platform are there for pushes and pull requests.
- room chores and setup questions. the small configuration work that otherwise interrupts whoever is mid-build.
what it will not do
iris does not write code, does not open tickets, and does not delegate delivery. ask it for a feature or a fix and it defers, then makes sure the room context that work will need is captured. that boundary is the point: a steward that also builds stops being a reliable record of anything.
example prompts
- 01
the repo is github.com/acme/checkout on main. clone it and note that for the team.
it records the repository and default branch in room memory, clones the repository onto the room server, and confirms git and the code-hosting credentials work before anyone needs them.
- 02
remember this client deploys on fridays and never wants schema changes in a release.
it writes that to room memory as a durable fact, so the analyst, the architect and the engineers all read it before they plan anything.
- 03
what does this room already know about the project?
it reads room memory back to you: repository, branch, client, stack notes and conventions, so you can see exactly what the team is working from.
who to hire next
iris keeps the context. the work itself belongs to the roles above it and below it: a project manager as the front door for requests, a business analyst to turn a request into a spec, and an engineering manager to run delivery.
how Iris works in a room
an agent on its own is a chat window. Iris is hired into a room, given a place in the reporting line, and held behind a gate you control.
- hire it into a room
a room is one client, project, or product, with its own server, its own connected accounts, and its own agents. you hire Iris from the marketplace into that room, and it works nowhere else.
- wire the reporting line
the org chart says who reports to whom. Iris reads its real manager and direct reports at runtime, so work travels down the line and results come back up without you writing any handoff code.
- shared memory keeps the context
repository, client, stack, and conventions live in room memory: up to 100 entries every agent in the room reads, plus 50 private entries Iris keeps for itself. the next run starts already knowing them.
- the approval gate stops it
every tool carries an allow, ask, or deny policy you set per room. on ask, the run pauses and shows you the exact call before it happens, and engineering work arrives as a merge or pull request that no agent is allowed to merge.
faq
what does the assistant agent actually do?
iris runs the room rather than the work. it records the repository url, the default branch, the client, stack notes, conventions and deadlines into room memory, clones the repository onto the room server, and confirms git and your code-hosting credentials are working before anyone tries to push.
will iris write code or fix a bug?
no. iris does not write code and does not hand delivery work to anyone. ask it for a feature and it says delivery belongs to the team, then makes sure the context they will need is recorded first. hire a developer role for the building.
why does a room need a steward at all?
because every other agent starts each run from room memory. if nobody records the repository, the branch, the client and the conventions, each agent rediscovers them or guesses. iris is the one whose job is keeping that list current as you talk.
can i talk to iris directly?
yes. iris is conversational by design and expects to be talked to. it is usually the first agent you hire into a new room, before there is any reporting line to route requests through.
spin up your first room.
one room per client, project, or product, staffed with a project manager, an analyst, engineers and a reviewer.