Agent Force
Agent Force is how you build and run teams of AI employees in Nexus. Each team is called a Force. A Force has a mission, a group of AI employees, and a playbook: the ordered steps the team follows for every job.
Explore this section
| Page | What it covers |
|---|---|
| Setup wizard | Creating a Force, step by step |
| AI Employees | The members of a team, their roles and trust |
| Playbooks | The steps a team follows |
| Triggers and schedules | Starting work automatically |
| Guardrails | Limits and budgets |
| Knowledge | What the team knows and which systems it can use |
Force or project?
A project groups chats and files. A Force groups AI employees. A Force can be linked to one project, and that project supplies its shared knowledge and memory. See Projects.
The Forces page
Click Nexus Agent Force in the left sidebar. The page is titled Forces: "Your AI teams — what each one is for, who works in it, and what it is doing now."
- New Force starts the setup wizard.
- Tabs: Active (n) (operating Forces), Drafts (n) and Archived (n). Counts follow your search.
- Search Forces matches the name, mission or description.
- Sort: Last activity (default), Name or Newest. Pinned Forces always come first.
- Cards page sideways, with dots, arrows and keyboard keys (arrow keys, Page Up/Down, Home, End).
What a card shows: a status pill (Operating, Draft or Archived), pinned and Shared markers, the name and mission, the project line, up to two AI employee chips (Idle or Working on N), and three counters: Working, Completed Today and Needs Approval. Drafts show Setup N of 4 instead. The link reads Open Force, Continue setup or View.
The ⋯ menu is available to the owner: Pin / Unpin, Archive, Delete (and Restore for archived Forces). Deleting asks "Delete this Force?" and cannot be undone.
| Situation | You see |
|---|---|
| No Forces | "No Forces yet", with a New Force button |
| No match | No Forces match "(search)". |
| Could not load | "Couldn't load your Forces" and Try again. Your Forces are not gone |
The same cards also appear on Nexus Home.
The Force workspace
Click a card to open the workspace at /nexus-force/(id).
Header
- ← Agentic Workforce goes back to the Forces page. A draft shows Draft · setup unfinished.
- Admin icons: Edit Force (pencil) reopens the wizard, and Reset team (circular arrow) clears the team's history.
- Make my own copy of this team (duplicate icon) is open to everyone who can see the Force.
- Hire member (admins) opens the hire form.
- People with limited access see Shared with you · Operate or Shared with you · View.
Draft Forces
A draft shows Saved as a draft ("Draft teams cannot run until activated. Add at least one member first."). Admins can click Continue setup, or Activate team once there is at least one member.
Project and teammates
- The Project card links the Force to a project. Admins pick one from the list ("No project (no knowledge base access)") or click + Create new project. Without a project, the team has no shared knowledge space.
- Teammates lists the people who can use this Force. Admins click Manage to Add teammate (search by name or email, 2+ characters) and choose a level:
| Level | What they can do |
|---|---|
| Viewer | See everything, change nothing, make their own copy |
| Contributor | Start jobs and answer or cancel decisions |
| Owner | Full control |
- Click a person's level badge to change it, or the X to remove them. Removing someone ends any connector loans they made and moves their AI employees to the owner's key.
- A personal Force shows "Personal — only you."
Missing roles
If the playbook needs a role nobody holds, a notice says "This team needs a member for the (role) role." with a Hire member button, or "No (roles) on this team." It is information only: the team still runs and skips those steps.
The tabs
The tab rail on the left has eight sections.
| Tab | What it is | Guide |
|---|---|---|
| Overview | What needs you, spending, ask the team | Below |
| Work | The playbook | Playbooks |
| Schedules and Triggers | Start work automatically | Triggers and schedules |
| Members | The roster | AI Employees |
| Shared Knowledge | What everyone on the team knows | Knowledge |
| Resources | Connected systems | Knowledge |
| Guardrails | Limits for the whole team | Guardrails |
| Activity | Cost and cases | Below |
The Overview and Members tabs show counters. The address keeps the tab (?tab=work), so links open the right one.
Overview
Check what needs you
At the top, Needs you says "N decision(s) waiting on you" with a Review in Approvals button, or "All caught up. Nothing waiting on you right now." Questions from your team appear here and can be answered inline. Click Show more if there are more than six.
Screenshot placeholderScreenshot to add: The Needs you area with a waiting decision and the Review in Approvals button. Read the numbers
Three tiles show spent all time (all members, including paused and archived ones), team members and cases handled.
Give your team a job
Type into the Ask your team box ("Ask your team, or hand off a job…") and click Give your team a job. A toast says "Your team is on it" and the Ask page (described below) opens. The box needs at least one active member, and viewers do not see it.
Find earlier asks
Recent asks lists recent jobs. Search with Search asks, filter by All, Working, Needs you, Done, Failed (and Cancelled when there are any), pick a date range, and choose 4, 8 or 12 per page. Empty: "No asks yet — Ask your team something, or let a trigger bring one in."
Needs you covers questions your team asked, queued connector actions and desktop approvals. Connector and desktop approvals are decided on the Approvals page, not inline. See Chat: Approvals.
Activity
- Cost shows spending per member for All time, 30d or 7d, with the number of cases and a total. "No spend recorded yet." appears when empty. Cost counts a member's whole session, while cases counts only team cases they took part in.
- Cases is the same list as Recent asks.
The Ask page
Click any ask to open its page at /nexus-force/(id)/asks/(run). It updates live while the work is running.
Header. The title is the first line of the request, with Show full request to see all of it and Copy request. A meta row shows the status, when it started, how long it ran, where it came from (Manual ask, Email, Schedule or Chat) and how many members took part.
| Status | Meaning |
|---|---|
| Working | The team is busy |
| Needs you | It is waiting for a person |
| Done | Finished |
| Failed | It did not finish |
| Cancelled | Someone stopped it |
Cancel ask (admins and contributors, while it runs) asks "Cancel this ask?": your team stops at the next step, and work already in progress may still finish. Choose Cancel ask or Keep working.
Waiting for you. When the team needs a decision you see its question with answer buttons and a free-text box, then Send. A toast says "Answer sent — your team is resuming". Your answer is saved as a precedent for similar cases. Viewers see "View only — waiting on a teammate with edit access to answer."
Outcome. The result shows as text with Copy outcome. Other states: "Draft awaiting approval", "The team's reply will appear here once it is ready.", "This ask finished without a written reply.", "This ask didn't finish" with the reason, and "Cancelled". Failed and cancelled asks have an Ask again button.
Path lists the steps the playbook took, in order, with the people involved and a time. Team has one card per member who took part, showing what they did and wrote (Copy reply is available). Technical details holds the step log and a link Open run graph for troubleshooting.
Copy, reset, archive and delete
- Make my own copy. Name the copy and its project and click Make my copy. You own the copy, which includes members, playbook and a snapshot of knowledge. Everyone starts in Shadowing. Mailbox triggers, connections and the AI key setting are not copied.
- Reset team asks twice, then you type the team name. It clears all case history, member chats, learned memories, decision precedents and waiting approvals. It keeps members, the playbook, project, teammates, schedules, coaching notes and shared knowledge.
- Archive, Restore, Delete are on the card menu. Schedules and standups of an archived Force stop firing.
More detail is in After You Deploy.
Who can do what
| Access | What it allows |
|---|---|
| Admin | Everything: edit setup, hire and manage members, playbook, schedules, triggers, standups, teammates, guardrails, knowledge, reset, archive and delete |
| Operate | Ask the team, answer and cancel decisions, cancel asks, "Try on past cases" |
| View | Read everything and make a copy |
The Force owner and platform administrators are admins. For a Force linked to a shared project, project owners are admins, contributors can operate, and viewers can view. A personal Force belongs only to its owner.