AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).
{
"section_id": "custom_tools",
"title": "Custom Tools",
"markdown": "**What it is:** When a job needs a tool the Executive doesn't have, it builds one on the spot rather than telling you it can't. A tool it is likely to need again, it keeps — those are your **custom tools**.\n\n**What it does:**\n\n- **Does repetitive work in one go.** \"Create a reminder for each of these renewals\", \"file every scan in this Drive folder\", \"check each of these people's open items\" — instead of working through the list one step at a time, the Executive builds a small tool for the job and runs it once. It's faster, and cheaper in AI usage.\n- **Works on files.** For work that needs real file libraries (splitting a PDF, building a spreadsheet, a Word or PowerPoint file, or a chart), it runs Python in a locked-down sandbox with no network access. These file jobs run only in the principal's own chats, never in workflows.\n- **Keeps what works.** When a tool it built did the job and the job will come up again, the Executive keeps it and says so. Next time it reuses the tool instead of building it again. Saving again under the same name adds a new version.\n- **Works in chat and in workflows.** A workflow step can use the same approach for a folder of hundreds of files. A kept tool is ready in the principal's chats straight away. A workflow can use it only after you switch on **Use in workflows** for it, and keeps running the version you switched on until you choose a newer one. Kept file tools (Python) never run in workflows.\n- **Stays inside the usual limits.** A custom tool can only do what the conversation or workflow using it is already allowed to do: the same tools, the same checks on who it reaches, the same approvals for anything new, and every action in the Audit Log.\n\n**Who can keep and run them:**\n\n- Only the principal's own chat turns can keep a tool, or run a kept one in chat. Someone emailing the Executive, or a teammate chatting with it, can't.\n- A workflow (scheduled runs included) runs a kept tool only after the principal switches on **Use in workflows** for it, and only when the workflow step already allows every tool the kept tool uses.\n- Only the account owner can open **Custom tools**. Anyone else sees *Only the account owner can see custom tools.*\n\n**How to use:**\n\n1. Just ask for the job — the Executive decides when building a tool makes sense. You can also say \"do that for all of them\" or \"keep that so you can do it again\".\n2. Ask \"what tools have you built?\" to hear what it has kept.\n3. Open **Settings → Advanced → Custom tools**. Each tool shows its name, what it does, its version, where it was saved from (a chat or a workflow) and when it was last updated, and which of your other tools it uses (a file tool says *Works on files with Python*).\n4. Click **Details, versions and runs** to see **How it works** (the tool's code), every kept **Version** with where it came from, and its **Recent runs** (worked or failed, version, number of tool calls, time taken). **Hide details** closes it.\n5. Use the switch at the top of a tool's card to turn it off or back on. On an earlier version, **Use this one** makes that version the one that runs; the current one says **In use**.\n6. Switch on **Use in workflows** to let your workflows use a tool. When the Executive improves it later, workflows stay on the version you approved until you click **Use version N in workflows**. Turning this on needs signed sign-ins on the server (or a local login), so that nobody else can turn it on for you.\n7. See how much work was done this way on **Token usage**, under **Done in one go** (jobs, actions taken, model turns avoided) and **Work on files** (file jobs, cost of those turns, CPU time, largest job).\n\n**Tips:**\n\n- A turned-off tool never runs, and stays off even if the Executive improves it later — only you turn it back on. Turning a tool off also switches off **Use in workflows**; the workflow switch can't be used while the tool is off.\n- Up to 200 custom tools are kept. Each keeps its 20 newest versions, plus the one in use and the one switched on for workflows.\n- An operator can switch the feature off with `CHAT_SCRIPTS=false` (building tools in chat), `WORKFLOW_STEP_SCRIPTS=false` (in workflows), `PYTHON_JOBS_ENABLED=false` (file jobs) or `SAVED_TOOLS_ENABLED=false` (keeping tools). With `SAVED_TOOLS_ENABLED=false`, the Custom tools page says so: nothing new is kept and none of the kept tools run.",
"mermaid": null,
"generated_at": "2026-10-15T21:00:00Z"
}