# AI use cases for Infomarchy (nixfred/infomarchy)

Repo: [nixfred/infomarchy](https://github.com/nixfred/infomarchy) | Use cases: 4 | Page: https://dedupedai.com/use-cases/nixfred-infomarchy/

Infomarchy is an Omarchy desktop plugin that draws live AI agent sessions, usage, rate limits and machine stats onto the wallpaper in your current theme.

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

- See every running AI agent on your wallpaper: https://dedupedai.com/use-cases/nixfred-infomarchy/see-all-running-agents-on-desktop/
- Find and stop agent sessions nobody is using: https://dedupedai.com/use-cases/nixfred-infomarchy/clean-up-stale-agent-sessions/
- Keep a large Grok Bot roster readable on the desk: https://dedupedai.com/use-cases/nixfred-infomarchy/tame-grok-bot-roster-on-desktop/
- Jump straight into agents running in tmux, Herdr or Boomux: https://dedupedai.com/use-cases/nixfred-infomarchy/jump-into-multiplexed-agents/

## How to see every running AI agent on your wallpaper with Infomarchy

Repo: [nixfred/infomarchy](https://github.com/nixfred/infomarchy) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Glance at the desktop to see which agents are working, their projects, and their resource use.

**Who it is for:** A developer running Claude Code in several terminals, Codex in another, and a local Ollama model, who loses track of what each one is doing.

**The problem:** Knowing the state of each agent means switching through windows, reading titles, or running monitoring commands by hand.

**The outcome:** Each running agent shows as a card on the desktop with its project, uptime, pid and a pulsing dot while it is thinking.

### Steps

1. Install Infomarchy by following the install instructions in the README.
2. Open the desktop and look at the Live AI Sessions cards, one per running agent.
3. Read each card for its project, working directory, uptime, pid and workspace number.
4. Press `SUPER + I` to hide the cards and see the plain wallpaper, then press it again to bring them back.
5. Click a card to focus that agent's terminal.

### Prompt to paste into your agent

```text
In the infomarchy repo, follow the README install steps on this Omarchy machine, then list the Live AI Sessions cards visible on the desktop. Expected output: one line per running agent with provider, project and pid. Verify that the count matches the number of agent processes you can see with the process list.
```

### Caveat

The excerpt does not include the install commands, so the first run depends on following the full README, and session data only appears for agents running on this local machine.

Risk, credentials: The desktop shows recent prompts and session details, so anyone who sees the screen can read what you asked your agents.

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/nixfred-infomarchy/see-all-running-agents-on-desktop/

## How to find and stop agent sessions nobody is using with Infomarchy

Repo: [nixfred/infomarchy](https://github.com/nixfred/infomarchy) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Spot idle agent sessions tagged STALE on the desktop and stop them with a confirmed right-click.

**Who it is for:** A developer whose machine has old Claude background sessions or Cursor workers left running for days after the work ended.

**The problem:** Idle agent processes keep using memory and clutter the desk, and it is easy to forget they are still running.

**The outcome:** Stale sessions are marked on their cards, and you stop them deliberately with a graceful stop or a process end.

### Steps

1. Look for cards tagged STALE with an idle time, such as idle 6h or more.
2. Right-click the stale card.
3. For a background Claude session, choose STOP SESSION, which uses `claude stop <session-id>` and keeps the conversation resumable. (inferred, check the README)
4. For any other stale session, choose END PROCESS, which sends SIGTERM after the helper confirms the pid.
5. Click the option a second time within four seconds to confirm. Nothing is stopped automatically.

### Prompt to paste into your agent

```text
In the infomarchy repo, identify one card tagged STALE on this machine and report its provider, pid and idle time without stopping it. Expected output: a short report with those three fields. Verify that the pid matches a live process before any stop action is taken by a person.
```

### Caveat

END PROCESS sends SIGTERM to a process, so check the card before confirming, since the README says stopping is never automatic but the action itself cannot be undone from the desktop.

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/nixfred-infomarchy/clean-up-stale-agent-sessions/

## How to keep a large Grok Bot roster readable on the desk with Infomarchy

Repo: [nixfred/infomarchy](https://github.com/nixfred/infomarchy) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Group quiet Grok Bot sessions into one card so Claude and Codex cards keep their full detail.

**Who it is for:** A user with many Grok Bot bots in the xAI desktop app, whose idle bots crowd the desk and shrink every other card.

**The problem:** Each bot gets its own card, so a large roster pushes the desk into dense layout and removes detail from active agents.

**The outcome:** Quiet bots collapse into one grouped card, and the rest of the desk keeps its working directory, host, git and pid lines.

### Steps

1. Open the Live AI Sessions area and find a Grok Bot card group, which shows a count of quiet bots.
2. Click the disclosure caret next to the provider name to turn grouping on or off.
3. Adjust the window that counts a bot as quiet by setting `sessionQuietMinutes` in `dashboard.json`. A value of 0 groups every idle session.
4. Check that the SESSIONS header reports the quiet count.
5. Right-click an individual bot inside an expanded group to open it in the inspector.

### Prompt to paste into your agent

```text
In the infomarchy repo, read the sessionGroups and sessionQuietMinutes settings in dashboard.json and report their current values. Expected output: the two values and the number of Grok Bot cards visible on the desktop. Verify that waiting and blocked bots are not inside a group.
```

### Caveat

Grouping is on by default only for Grok Bot, and the other attributes of bots are counted once per shared process, so their CPU and RAM show as a dash on most cards.

Risk, credentials: Grok Bot cards show the last line each bot wrote, so unread replies and bot text are visible on the screen.

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/nixfred-infomarchy/tame-grok-bot-roster-on-desktop/

## How to jump straight into agents running in tmux, Herdr or Boomux with Infomarchy

Repo: [nixfred/infomarchy](https://github.com/nixfred/infomarchy) | Difficulty: Advanced | Time: 1 hour | Basis: From the README

Click an agent card to focus its window and land on the right pane, tab or workspace.

**Who it is for:** A developer who runs agents inside tmux, Herdr or Boomux and needs to reach the right pane fast without hunting through panes.

**The problem:** Agents hosted inside a multiplexer are hard to find, and the terminal window does not show which pane holds which agent.

**The outcome:** Clicking a card focuses the terminal window and moves to the matching tmux window and pane, Herdr workspace, tab and pane, or Boomux workspace.

### Steps

1. Start the agent inside tmux, Herdr or Boomux as you normally do.
2. Find its card on the desktop and read the host line, such as tmux session:window.pane or the Herdr workspace, tab and pane.
3. Click the card to focus the terminal window.
4. The jump runs `tmux select-window`, `tmux select-pane` or `tmux switch-client` for tmux, or the matching Herdr socket calls for Herdr, or `boomux open <workspace>` for Boomux. (inferred, check the README)
5. If the card says no client window found, open the matching terminal window and click the card again.

### Prompt to paste into your agent

```text
In the infomarchy repo, find one agent card hosted in tmux and confirm that its host line shows session:window.pane. Expected output: the tmux target string and the matching client terminal title. Verify that the clicked card focuses the same pane that the tmux target names.
```

### Caveat

Remote processes on another machine are not shown, and Boomux behavior is described for version 1.9.7 in the README, so other versions may differ.

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/nixfred-infomarchy/jump-into-multiplexed-agents/