Once an AI assistant is doing a share of the work, the project tool has to treat it like the rest of the team: something you can hand a card to, mention, check up on, and switch off. Most tools bolt an assistant onto the side of the product instead. Here is what to look for, and how NovumOS does it.
An agent on NovumOS is a user of kind “agent.” It appears in assignee pickers and mention dropdowns, shows up as the actor in card history and the activity feed, and holds its own membership and role, the same as a person. Ask Claude to plan the week, hand an assistant the invoices to chase or the alt text to write, and read exactly what it did on the card. Nothing happens anonymously, and you can hand a client or a manager the same trail you see without exporting anything.
Each agent authenticates with its own bearer token, shown once and stored hashed. Its permissions are capped by the role of the member who owns it, and it can be granted viewer or editor access on a single board, so a pipeline that should only touch one column never sees the rest of the workspace. Pausing the agent stops every one of its tokens at authentication, reversibly, and the kill switch is on every plan. What an agent seat is explains the model in full.
Every card holds a block tree, so the brief, the draft, and each revision live on the card instead of in a document linked from it. That is what makes the agent useful rather than merely connected: it can read the brief, write the draft into the same card, and move it to Review, and a person can see all three in one place. Clients follow their work through seatless share links, so a client portal costs nothing.
Every seat is a flat $1 per month billed annually ($12/yr), or $3 month-to-month, the same for humans and agents. The first agent is free on every plan. There is no per-call metering and no AI-credit meter, so a night spent clearing a backlog costs the same as a seat that sat idle. For the arithmetic on a real team, see why every seat is $1.
Everything an operator does in the UI has an API equivalent. Developers may know the category as kanban; the product speaks “board” to its operators. The MCP server at /v1/mcp/http exposes a typed tool for every REST endpoint, webhooks carry the changed fields inline, and a column can be drained as a durable work queue. The API checklist covers that side.
Give your assistant a seat on the board. The first one is free on every plan, and no card is required.
Create account