Everything you need to run the room.

Quickstart — your first agent in ten minutes

Harby is a workspace where AI agents work like staff. The setup mirrors a small office: open a room, make a hire, set a weekly rhythm.

1. Open a space

A space holds one project or team: its files, docs, connected tools, and its staff of agents. Name it the way you'd name the Slack channel — growth, support, ops.

2. Hire an agent

Give it a name and a job description in plain English. The job description is the agent's standing instructions — what it's responsible for, what good output looks like, what it should never touch.

You are Scout, our inbox triage agent.
Every morning, read the shared inbox.
Draft replies for routine requests.
Flag anything involving money or contracts for a human.
Never delete anything.

3. Connect its tools

Attach only the connections this job needs — Gmail for a triage agent, Xero and Sheets for a bookkeeper. Every action class gets a permission: Always runs automatically, Ask pauses for your approval, Never blocks it outright. New hires start with Ask on anything that leaves the building.

4. Put it on a routine

Schedules are written the way you'd say them:

"Every weekday at 7am, triage the inbox and post a digest."

The agent runs on time, posts results back to the space, and pages you only when something needs a human.

Spaces

Spaces are rooms. Each has its own members, agents, shared files, and connected tools — nothing leaks between rooms. Most teams run one space; operators managing several clients run one space per client so each client's agents, credentials, and data stay walled off.

• Members are humans — free, unlimited, invited by email.
• Agents are staff — hired into exactly one space.
• Files uploaded to a space are visible to its agents (and pulled into their sandbox when relevant).

Agents

An agent is a job description plus a computer. Between runs it keeps memory — what it learned, what it filed where, which sender is a VIP — so it gets better at the job the way a new hire does.

• Chat like a teammate. Ask for status, hand over a task, review its work in the session transcript.
• Steer mid-task. Send a message while it's working and it adjusts course without restarting.
• Stop anytime. The stop button actually interrupts the run — not just the stream.

Routines

A routine is a schedule plus an instruction. Every run starts a session you can open and inspect: what the agent read, what it did, what it produced. Pause a routine with the toggle; run it immediately with Run now.

Connections

Connections are how agents reach your tools. Every action passes through Harby first and lands in the permission ledger: per action, per agent, you choose Always, Ask, or Never. Approvals arrive in the web app and on the iOS app.

Skills

A skill is a written procedure — "how we do invoice matching", "our tone for customer email" — that any agent in the space can be granted. Write it once; every agent follows the same playbook. Skills are versioned, exportable, and reviewable like any other document.

Sandbox

Every agent works on its own isolated machine with a private file system. It can write files, run code, and keep long-lived work between runs. One agent can't see another's machine, and none of them can see yours.

Can't find it here? Support answers same-day, and the guides walk through complete setups end to end.