Roadstar for agents

Roadstar is a staff of AI agents for one small-business owner: a design studio, a dental practice, a bakery. Roadstar is the owner’s chief of staff, and it makes the other agents. These docs are for those agents, and for any agent working with Roadstar from outside.

Where you might be running

You are	Your tools	Read first
An agent’s chat	Hand-offs, threads, routines, notes, memory. No work tools: a chat sends work and answers.	Chats and threads
Roadstar’s chat	The same, and make_agent and change_agent	Agents and the chart
A thread	Every tool group, through browse_tools, find_tools and use_tool	Finding and using tools
A program on the owner’s Mac, or an outside AI app	A thread’s tools, through Roadstar’s MCP server	Macs and outside AI apps

All tools shows every tool and where it is offered.

The examples

The examples follow one business. Fernhill Studio is Sam Rivera’s design studio. Besides Roadstar, Sam has three agents:

Agent	Job
Client desk	Answers new and current clients, and keeps Contacts and Companies up to date
Proposal writer	Prices and writes proposals and quotes from the rate card
Bookkeeper	Sends invoices on time and chases what’s overdue

Their clients include Juniper Dental and Ortiz Bakery.

Reading these docs as an agent

• Every page is markdown at its address with .md added: /tools/mail.md. The plain address gives markdown too when you send Accept: text/markdown.
• /llms.txt lists every page with a line on each. /llms-full.txt holds every page in one file.
• /tools.json has every tool’s input, result type and owner’s yes, as data.
• Inside Roadstar, the help group searches and reads these pages.

What’s here

• How it works: agents, chats and threads, hand-offs, tools, the owner’s yes, Home, routines, memory, and Macs.
• Tools: one page per group, each tool with its input, limits, owner’s yes and result.
• Use cases: seven pieces of Fernhill Studio’s work, call by call.
• Reference: limits, models and errors.