Back to the Field Manual
Anyone choosing an AI app

Which agent path fits your work?

Compare ready-to-use assistants, reusable Bot instructions and tools for software builders. Choose one that fits the job you need done.

6 min readUpdated 2026-09-20Sources linked

Choose an assistant, a Bot or a builder tool

You do not need to build your own AI system to benefit from an agent. A service may already handle your job. Saved instructions may help an assistant do the same job more than once. Tools for software builders matter when you are making a product or need control that a ready-made service does not offer.

Choose the simplest option that can do your job. These examples come from public product descriptions; Bot Cabinet has not ranked the services or tested them hands-on.

Ask a ready-to-use assistant

Meta describes Muse as a personal agent with background work, connected apps and a dedicated cloud computer. Its September 8 announcement describes a US rollout on iOS, Android and web, plus WhatsApp messaging, free access and subscription options. Confidential VM, Shop Pay and 1Password support were future additions in that announcement—not capabilities this guide verifies as available.

Instinct describes an assistant you text or call, with connected context and proactive follow-up. Its public start link leads to sign-in. We have not verified a generally available price or whether a particular person's accounts and devices are supported. Treat those as questions to resolve before committing.

Consider this path when you want a result rather than another system to administer. First check your actual services, the access required, what happens before a send or purchase, and how to disconnect and delete stored information. A simple chat interface does not eliminate those decisions.

Ready-made assistants are splitting into different jobs

These new assistants do different jobs even when companies use similar words. Ollie focuses on families and shared household information. Wajo's Fo focuses on errands such as calls, bookings, purchases and dealing with vendors. Town focuses on learning how a person works, then helping across email, calendars, documents and business tools.

For a family assistant, check that everyone can participate and that it uses accurate household information. For an assistant that calls or buys things, set spending limits and confirmation rules, and check that it asks for help when a merchant or phone menu blocks it. For a work assistant, check its account permissions and saved memory, including how to correct what it has learned about your voice, contacts and priorities.

These descriptions come from the companies. Bot Cabinet has not tested or endorsed the services, and other assistants are available.

  • Family coordinator — compare with Home Admin, which organizes lists, reminders and research but does not claim to connect a whole family or act on its own.
  • Real-world concierge — compare with the Personal Planning Desk, which prepares choices and plans while a person controls calls, bookings, purchases, cancellations and messages.
  • Work assistant — compare with the Small-Business Admin Desk, which prepares work for review and requires approval for outside actions. It does not learn from connected accounts as a ready-to-use service.

Use saved Bot instructions

Grok Bot's official guide explains how to share instructions, selected memories, skills and plugins. A template still needs review and setup. Special scripts or connections may not move to another service. Bot Cabinet's Grok downloads are step-by-step build guides, not Grok template links.

A portable skill is a folder of instructions and helpful files for an AI agent. Check that your app supports its instructions and tools. Test each skill and, for a crew, test how the Bots pass work to one another.

Use saved instructions when you need to repeat a job with the same sources, output format and approval rules. Check for an existing workflow before making another. Review a sample answer, setup requirements, recurring costs and how to stop it.

Tools for people who build software

A harness is the code around an AI model. It decides what tools the model can use, what information it sees, when it keeps going and when it stops or asks for help. Software companies do not always use the word in exactly the same way.

Jev is one tool for software builders. TypeSafe says it helps a system choose or score options; it does not write the final answer. LangChain showed an early example of using it inside a larger system. Consider it when you are building software that needs to choose between options.

Try the same job and compare results

  • Name one real job and the answer, file or action you need. Include what must not happen without your approval.
  • List the accounts, data, devices and permissions it needs. Check those exact connections rather than assuming broad integration claims cover them.
  • When the service allows a test, start with safe sample material and do not let it send messages or make purchases on its own. Compare it with your normal way of doing the work.
  • Record setup effort, corrections, human review time, charges and whether the output was actually useful. Repeat the same job on a second and third real occasion before calling it a dependable routine.
  • Check what happens after interrupted work, changed instructions or expired access. Know how to stop schedules, correct memory and export or delete information.

Find a Bot for your job

Use the Fit Test to choose a Bot or crew. Browse examples of jobs they can help with, then check the Proof Room for saved test results and testing limits. You can also use an outside service if it already does the job you need.