Connect an Assistant
Let Claude, Cursor or Codex read your trees, sites and estimates, and run jobs against your real account.
You already have an AI open all day. Connect it to your account and ask it about your work instead of going to look it up.
Takes about a minute. There is nothing to install and nothing to download.
Setting it up
Assistant → Connect an assistant, then:
- Where will you use it — Claude Code, Claude Desktop, Cursor or Codex CLI.
- What it can do — read only, or read and draft.
- Create it. You get a block to copy. The screen tells you exactly where it goes and what to restart.
The connection is a key. It is shown once, at creation, and the block you copy has it inside. Lose it and you make another. Revoke one on the API keys screen and it stops working on the next request.
What each scope allows
Read only answers questions and changes nothing. Which sites have oaks due a crown clean, what you quoted the last removal at, how many customers you have.
Read and draft also adds customers and sites and writes draft estimates, which is what you want when you are working from a spreadsheet somebody emailed you.
Neither scope can send an invoice to a customer. That stays deliberate, on the API keys screen, where you have to go and choose it.
What it can never do
Nothing deletes. There is no way for an assistant to remove a record, void an invoice or cancel a job, because no such tool exists.
Every tool that changes anything asks you first. That is not a setting you can turn off; a tool that skipped the confirmation could not be added to the product at all.
ChatGPT and claude.ai
Not yet. They connect from their own servers rather than from your computer, so they need a sign-in flow instead of a key. The four above run on your machine, which is why they work today and why your key never leaves it.
Next
Start with Playbooks, which are whole jobs already written for you.