Works with the assistant you already use.
Connect your AI assistant to the same customers and jobs your crew sees, bring your work over from the tools you use today, and take your records with you whenever you like. Scoped keeps named setup paths for Codex and Claude Code, each tested against the client’s own commands.
Two named setup paths, maintained and tested.
The list is short on purpose: a tool is named here only when Scoped maintains and tests its setup, not because the standard would technically allow it.
Ask where a job stands before you pick up the phone.
Scoped doesn’t run the AI. The assistant runs in its own tool; Scoped is the record it reads and the place its permitted updates land. It doesn’t work on its own, and it never sends anything to your customers. Read where the agent runtime ends and Scoped begins.
A connected assistant can
- Tell you where every job stands, off the live pipeline rather than someone’s memory.
- Pull up a customer’s history before you call back: past jobs, open quotes, the notes someone left.
- Update the next step on a job, change its status, and add a comment the rest of the team sees.
- Find the work that stalled: the quote nobody chased, the job that hasn’t moved in weeks.
You stay in control
- You approve the connection yourself, for one workspace at a time, after reading what it asks for.
- Scoped checks the grant, your membership, the workspace, and the permission on every request.
- Every change records the authorizing person and the connection it came through.
- Revoke a connection and future access through it stops at once.
Bring your work in. Take it with you.
Put your assistant on the real jobs.
Create a free workspace, add a few customers and jobs, then connect your assistant and ask it something read-only first.