# AI use cases for Agents Office (ajsahni/agents-office)

Repo: [ajsahni/agents-office](https://github.com/ajsahni/agents-office) | Use cases: 4 | Page: https://dedupedai.com/use-cases/ajsahni-agents-office/

Agents Office is a local, 3D isometric office of 35 AI agents in six departments that do real work on your own Claude login, reading and filing notes in a folder you own.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Hand a task to the right agent in plain words: https://dedupedai.com/use-cases/ajsahni-agents-office/delegate-a-task-to-a-department-agent/
- Run inbox triage on a daily schedule: https://dedupedai.com/use-cases/ajsahni-agents-office/schedule-recurring-inbox-triage/
- Teach agents your standards with skills and briefs: https://dedupedai.com/use-cases/ajsahni-agents-office/teach-agents-your-standards/
- Rename and retarget agents with Claude Code: https://dedupedai.com/use-cases/ajsahni-agents-office/rename-and-retarget-agents-with-claude-code/

## How to hand a task to the right agent in plain words with Agents Office

Repo: [ajsahni/agents-office](https://github.com/ajsahni/agents-office) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Type a task in the task bar and the office routes it to a named agent that files the result in your notes.

**Who it is for:** A solo founder or small team lead who has a recurring piece of work, such as a proposal or report, and wants an agent to take it without writing a detailed prompt.

**The problem:** Writing a good prompt, picking the right assistant and finding the context each time takes effort, and results are scattered across chats.

**The outcome:** A deliverable from a named agent in that department's chat, plus a note in your brain folder that records the result and the tools used.

### Steps

1. Run `git clone https://github.com/ajsahni/agents-office.git` and then `cd agents-office`.
2. Run `./setup` (checks Node, git and Claude, installs, builds and boots once). Without it, run `npm install && node build.mjs && npm start`.
3. Run `npm start` and open http://localhost:4520. Confirm the panel shows LIVE · CLAUDE.
4. In the bar at the top of the panel, pick a department, type a task in plain words, and press Add.
5. Click the agent that picks it up to read the deliverable, and check the note in your brain folder.

### Prompt to paste into your agent

```text
Clone https://github.com/ajsahni/agents-office, run ./setup then npm start, and open http://localhost:4520. Add the task '<task in plain words>' to the <department> department in the task bar and report the agent's name and the note filed in the brain folder. Verify the panel shows LIVE · CLAUDE before you add the task.
```

### Caveat

This is a Beta that runs on your own Claude login, and the license is noncommercial, so it cannot be sold or built into a paid product.

Risk, credentials: Connected accounts such as Gmail or Slack are used by agents on your machine, so authenticate only the accounts you are willing to let the office read.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ajsahni-agents-office/delegate-a-task-to-a-department-agent/

## How to run inbox triage on a daily schedule with Agents Office

Repo: [ajsahni/agents-office](https://github.com/ajsahni/agents-office) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Set a routine in the Emails department so the office sorts the inbox at a fixed time each weekday.

**Who it is for:** A busy professional who checks email first thing each morning and wants a short list of what needs a reply before starting work.

**The problem:** Triaging the inbox by hand every morning eats time, and important messages get missed when the day starts.

**The outcome:** A routine that runs on the office's clock and reports what needs you, shown as SCHEDULED in the Task Status panel.

### Steps

1. Complete the setup in the first use case so the office is running at http://localhost:4520.
2. In the task bar, choose the Emails department and type a line such as: every weekday at 8am, triage the inbox and tell me what needs me.
3. Check the hint line, which reads the schedule back, then press Add.
4. Find the SCHEDULED chip in the Task Status panel to confirm the countdown.
5. Use the lead's chat to pause, resume, run now or delete the routine by name.

### Prompt to paste into your agent

```text
Use the agents-office repo at https://github.com/ajsahni/agents-office running at http://localhost:4520. Create a routine in the Emails department for '<schedule and task>' and report the routine's name and next run time. Verify it appears as SCHEDULED in the Task Status panel.
```

### Caveat

Routines run on this machine's clock, so the office must be running at the scheduled time for the routine to fire.

Risk, credentials: A scheduled routine can read connected mail on its own clock, so check what it may touch and use the needs-my-OK step where offered.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ajsahni-agents-office/schedule-recurring-inbox-triage/

## How to teach agents your standards with skills and briefs with Agents Office

Repo: [ajsahni/agents-office](https://github.com/ajsahni/agents-office) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Give agents a brief or a skill so their output follows how you actually work.

**Who it is for:** A team lead whose first agent results are generic and who wants them to match a house style, template or set of red lines.

**The problem:** Out of the box agents know only a one-line job, so results need heavy rewriting before anyone can use them.

**The outcome:** A skill folder or brief that the agent reads before each task, plus a feedback file that records your corrections as rules.

### Steps

1. Open your brain folder and create a skill folder under Agents Office/skills with a SKILL.md file and the template beside it.
2. Bind the skill to an agent or department in its front matter, or add a brief field to that agent in office.agents.local.json.
3. Run `npm run check` to validate the skills and briefs.
4. Open http://localhost:4520/api/skills to confirm who has which skill.
5. Send a deliverable back with `revise: ...` in the agent's chat so the correction is recorded as a standing rule or a one-off. (inferred, check the README)

### Prompt to paste into your agent

```text
In the agents-office repo at https://github.com/ajsahni/agents-office, write a skill for the <agent name> agent from the example document <path to example>. Run npm run check and report the skill file created and any validation errors. Verify http://localhost:4520/api/skills lists the skill for that agent.
```

### Caveat

Skills and briefs take effect on the next task with no restart, but agents only use what is in your brain folder and the shipped roster.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ajsahni-agents-office/teach-agents-your-standards/

## How to rename and retarget agents with Claude Code with Agents Office

Repo: [ajsahni/agents-office](https://github.com/ajsahni/agents-office) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Describe a new role in plain words and let Claude Code update the agent roster for you.

**Who it is for:** An operator who wants the office's 35 seats to match their real work, such as turning inbound sales seats into wholesale account seats.

**The problem:** Editing the agents file by hand is slow, and mistakes in ids or departments break the office.

**The outcome:** A local roster file with your renamed agents and retargeted roles, validated and loaded after a restart.

### Steps

1. Run `cd agents-office` and then `claude` to open Claude Code in the folder.
2. Say what you want, for example: Rename the Newsletter agent to PODCAST NOTES and say what it does.
3. Let Claude Code write the changes to office.agents.local.json and validate them with `npm run check`.
4. Restart the office with `npm start` and open http://localhost:4520 to see the new names at the desks.
5. Keep the local file out of git, since it is ignored and git pull will not overwrite it.

### Prompt to paste into your agent

```text
In the agents-office repo at https://github.com/ajsahni/agents-office, rename the agent <current name> to <new name> and rewrite its role for <new purpose>. Run npm run check and report any validation errors. Verify the new name appears on its desk after npm start.
```

### Caveat

Edits to id, department or lead are ignored and the server says so at start, so only change names, roles, what agents do and their tools.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/ajsahni-agents-office/rename-and-retarget-agents-with-claude-code/