---
name: busy-app-ui
description: Load before you tell the user where something is in the Busy app or how to do something in it, e.g. opening settings, connecting an app, managing skills, routines, files or memory, watching or controlling your screen, creating, organizing or deleting a bot, or signing out.
title: busy-app-ui
canonical_url: https://skilld.dev/gh/matisolina/busy/busy-app-ui
last_updated: 2026-11-12T03:00:58.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install matisolina/busy/busy-app-ui`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/busy-app-ui`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/matisolina/busy/busy-app-ui) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/busy-app-ui`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/busy-app-ui --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/busy-app-ui --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# The Busy app: real paths only

This is a map of the Busy hub interface checked against its code. Give the user only paths listed here. If what they ask for isn't here, say you're not sure where it is rather than guessing a menu, button or setting. Labels below are the exact on-screen words.

## Layout

- **Sidebar** (left): "Your bots" lists the bots; a "Create bot" button adds one. The sidebar can be collapsed and expanded with its toggle ("Collapse sidebar" / "Expand sidebar"). On a phone it opens from the menu button in the chat header.
- **Chat** (center): the selected bot's conversation. The header shows the bot's avatar and name and a **Bot settings** button (sliders icon) on the right. Files can be dragged onto the chat to send them to the bot.
- **Bottom of the sidebar**: the account button (avatar and name) and, next to it, a grid-plus button labeled **Skills, plugins and MCPs**.

## Account menu and Settings

- Click the account button at the bottom of the sidebar. The menu has the AI connection entry, **Settings**, and the sign-out item.
- **Settings** has these tabs: **Model**, **Skills**, **Plugins**, **MCPs**, **Usage**.
  - Model: the AI provider and model.
  - Skills: skills installed for the Busy app, including skills saved from chat; each can be enabled, disabled or removed. The built-in `find-skills` is listed here too.
  - Plugins: installed plugins.
  - MCPs: connected apps.
  - Usage: usage information.
- Skills, plugins and connected apps are shared by every bot in the app. There is no per-bot assignment.

## Connecting apps (MCP)

- The **Skills, plugins and MCPs** button at the bottom of the sidebar opens **Your toolbox**, with the user's **Connected apps** and the **Integrations** catalog (filterable).
- Each app card shows **Connect** (or **Connect with OAuth**, or **Add**), **Connected**, or **Connection needs attention**. A connected app can be disconnected with **Disconnect**. Some apps ask for credentials before connecting.
- If an app needs reconnecting, point the user here.

## Bot settings (per bot)

Open the bot's chat, then the **Bot settings** button in the chat header. The panel is titled "<bot name> settings" and has these tabs:

- **General**: name, identity and description; **Save changes**. **Delete bot** is at the bottom: it asks "Delete <name> for good?" and needs a second click. Deleting is permanent.
- **Live**: the bot's computer screen, live (available only while the bot is ready). **Take control** lets the user use the mouse and keyboard on it; **Done logging in** hands control back after a login. A "Mode" control and "Type on the computer" help with typing, including on a phone.
- **Library**: files in the chat, filterable by **All files**, **Generated by bot**, **Sent by me**, each with a download button.
- **Routines**: the bot's routines. Each row's options menu has **Edit**, **Pause** / **Resume**, and **Delete** (with a "Delete routine?" confirmation). New routines are created by asking the bot in chat.
- **Memory**: what the bot remembers; the user can add a memory (**Add memory**) or delete one.
- **History**: search through earlier messages of this chat.

## Logins and taking control from the chat

When the bot asks the user to log in, a card appears in the chat with **Take control** and **Done**. Take control opens the live screen; after logging in, the user taps **Done logging in** in the live view (or **Done** on the card). The card then says "You logged in. It goes on from there."

## Organizing bots

- Right-click in the bot list to **Create section**; right-click a section header to **Rename section** or **Delete section**. Bots are dragged into sections ("Drop bots here.").
- There is no hide or archive for a bot. Removing one means **Delete bot** in its General tab.

## Not in the app

These don't exist in the hub; don't send the user looking for them: a button to reset or restart the bot's computer, a per-bot capabilities list, a form to create routines, keyboard shortcuts for settings. If the user needs one of these, say it isn't available in the app.
