The built-in toolkit
Dates, arithmetic and email. Nothing to connect, and email is guarded three ways.
Every other connection attaches something you run. This one is AgentOS itself, so there is no host, no key, and nothing that can fall out of sync. Add it and the tools are there.
What it gives an agent
- •Today's date and time. A model has no clock. Without this it guesses, and guesses wrong.
- •Date arithmetic — move a date forward or back by days, weeks, months or years.
- •The gap between two dates — how many days, and which way round.
- •A calculator. Real arithmetic instead of the model's own, which is wrong in the worst possible way: confidently, and looking exactly like an answer.
- •A reference code generator — a random reference for a booking or ticket number. It is random, not checked against anything, so confirm it is free if the column is unique.
- •Send an email.
Everything except the email is a pure function. It reads nothing and changes nothing, which is why those are classed as reads and never queue for approval.
Set the timezone
Timezone takes an IANA name such as Asia/Dhaka, and it decides what "today" means for every date tool here. It defaults to UTC, which is rarely what anyone wants — set it when you create the connection.
Email is guarded three ways
Sending is the only thing on this platform that cannot be undone. A wrong row in a database can be corrected; a sent message cannot be recalled. So:
Recipients are checked against a domain allow-list, and the list starts empty. Empty permits nothing rather than everything, so a connection you have not finished configuring cannot email the world. Domains match exactly — acme.com does not cover mail.acme.com. List both if you need both.
The recipient count is capped, counting everyone copied. Five by default, so a mistake reaches a handful of people rather than a mailing list.
Sending needs human approval by default, because it is classed as an action and marked high risk. You can relax that on the tools page. The platform will not relax it for you.
Reply-to is optional — set it if replies should go somewhere other than the sending address.