Projects

Every agent belongs to a project. You don't create projects: the first time an agent starts in a repository, Agentower makes a project named after it, in the Building lane.

#The Projects page

Projects — in the sidebar, or the Projects view next to Board and Network at the top of the Agents page — shows every project in three lanes — Building, Live and Shelved — with how many agents are open in each or when it was last active. Move a project between lanes with its menu; lanes are for your own tidiness and don't change how agents are shown.

Open a project to see its page: today's sessions and tokens, the last 7 days, its open agents and its recent history — and its settings.

#Unsorted

Agents started somewhere that isn't a project — your home folder, or a folder that holds several repositories — go into a project called Unsorted. See Agents in Unsorted to fix it.

#Rename a project

On the project's page, change its name (1–80 characters). The short ID prefix (such as BIL) stays the same, so IDs your team already knows keep working.

#Agent chats

Whether you can read agents' questions and messages, and answer and message them from Agentower, isn't a project setting: it's one workspace setting, Agent chats, that an owner switches in Settings → Workspace for every project, new ones included. See Switch on Agent chats.

#Work details

Off by default. With it on, the project's work record also names the files changed, commit messages, the branch, pull request links and failed tests — not just counts — and keeps the first 600 characters of the instruction that started each turn and of the agent's closing summary, with secrets replaced by [hidden] on the computer before they're sent. Only owners and the project's approvers see them. Never code, diffs or command text. Owners and the project's approvers can switch it; switching it off deletes the names, instructions and summaries already kept.

#Read agents' replies aloud

On the project's page, switch on Read agents' replies aloud to hear each new agent message in that agent's own voice while its chat is open. It's a choice for your browser only (nothing is saved on the server), uses only voices on your device, and needs Agent chats on. For more natural voices, see Spoken alerts.

#Warn when agents overlap

On by default. When two or more agents are working in this project at the same time, the board marks their cards and shows a line above the sections, and channels with Agents overlap ticked get a message (at most once an hour per project). Switch it off on the project's page for a project where several agents at once is normal — for example one split into separate folders. It applies to everyone in the workspace; owners and the project's approvers can change it, and each change is in the audit log.

#Who may approve

By default every approver in the team can answer this project's agents. You can limit the project to named approvers instead — see Roles and approvers.

#Project guardrails

A project can have its own limits on session length, tokens and cost. See Guardrails.

#Merge or delete a project

At the bottom of a project's page, Danger zone has two actions. Only the workspace's owner sees them — on your own (Solo), that's you. Both need a sign-in from the last 7 days, and you type the project's name to confirm. Both are in the audit log, with numbers only.

Merge into… — for two projects that are really one (for example a repository that was renamed, or cloned under a different folder name). Choose the project to keep, and this one's agents move into it, keeping their IDs (such as OLD-04). Its named approvers join the other project's list when both are limited to named approvers; otherwise the other project's setting applies. Its guardrail moves too, unless the other project already has one. Its token and cost totals are added to the other's. From then on, new sessions that start in the old repository land in the project you kept, so the old project doesn't come back. You can merge while agents are open; they carry on in the other project.

Delete project — deletes the project and everything recorded for it: its agents and their history, timelines, usage totals, approvers, guardrail and chats. It can't be undone; take an export first if you want a copy. The audit log keeps one line, such as "Deleted project Storefront (12 agents, 3 subagents)". You can't delete a project while any of its agents is open — close them, or wait for them to finish, first. If an agent starts in that repository again later, Agentower makes a new, empty project for it.