AI clients and agents
AI client tools
Every tool an AI client gets when it connects to Ahamo, what it does, and which ones need a connection that may make changes.
On this page
These are the tools an AI client sees after it connects to Ahamo. Tools under Working on apps (changes) appear only on a connection allowed to make changes in development; every other tool reads.
Reading is free. Tools that start Ahamo's AI spend the workspace's credits exactly like the chat; they are marked
credits below. No tool writes production data, because production changes only through publish.
Availability. As for AI clients, your organisation decides whether clients may connect, read only, or make changes in development.
Account and workspaces
| Tool | What it does |
|---|---|
me | Who the connection acts as, its options and your workspaces |
list_workspaces | Your workspaces |
get_workspace | A workspace's name, and its plan and credits if you may see billing |
security_center | Your organisation's Security center, with every workspace's apps with their open issues and last scans, or every open issue filtered by workspace, severity, category or OWASP category. Needs permission to read the organisation's audit log; not on a connection limited to one app |
Reading apps
| Tool | What it does |
|---|---|
list_apps | The apps in a workspace |
get_app | An app's state, addresses and a screenshot |
list_templates | The workspace's app templates |
list_files, read_file | The app's source files (up to 2 MB a file) |
get_diff | Saved versions and what changed |
list_tables, describe_table | The data structure, never rows |
list_migrations | Data structure changes in development and production, and what the next publish applies |
data_rules | Who may read and change which data |
query | One SQL statement, with development reads and writes, production reads only (see below) |
list_extensions | The database's Postgres extensions |
logs | The app's recent logs |
advisors | Findings of the security and code checks |
list_functions, get_function | The app's server code |
files | The app's Files library |
list_settings | Secret names (never values) and variable values |
list_integrations | Connected accounts linked to the app |
list_chats | Your chats with Ahamo's AI in a workspace (yours, shared or all), with title, private or shared, what each is about and when it was last active |
list_turns, get_turn | A chat's turns and plans (chat_id, or an app's own chat by app_id), optionally waiting for one to finish |
list_skills, get_knowledge | The workspace's skills and what Ahamo's AI knows about the app |
app_analytics | Visits and requests over the last hour, day or week, as counts |
logs, files, query and list_extensions follow the app's AI access setting for each environment. Writes
through query need a connection that may make changes.
Working on apps (changes)
| Tool | What it does |
|---|---|
create_app | Credits. Starts a new app from a prompt, a template or a GitHub repository (repository_url). With a prompt, Ahamo's AI plans it first. A public repository comes in at once; for a private one the result links to the app, where you click Connect GitHub. Ahamo's AI then reads the repository and asks its questions in the chat one at a time, and the client follows them with list_turns and get_turn and answers each with send_message. A Supabase project found in the repository shows a Connect card in the chat, which you click in Ahamo. Not on a connection limited to one app |
send_message | Credits. Sends a message to Ahamo's AI in chat, plan or build mode, in a chat (chat_id), in an app's own chat (app_id), or with neither in a new private chat it starts in the workspace. Never approves a plan |
approve_plan | Credits. Builds a plan the chat proposed, as the plan card's Build this plan does, in the chat that proposed it |
edit_file, write_file, write_function | Credits. Propose code changes, as pending changes in the chat |
propose_migration, propose_data_rule | Credits. Propose a data structure or access rule change, applied to development first |
publish | Publishes the last saved version, with the same checks and approvals as in Ahamo. When the workspace requires approval it answers that approval was requested, and a person approves in Ahamo |
export | Starts Download App; you download it in Ahamo when it is ready |
set_variable | Sets a development variable; secret-looking values are refused |
request_secret | Returns where you enter a secret yourself; the value never passes through the client |
upload_file | Adds a file to the app's Files library (up to 10 MB through the client) |
link_integration | Returns where you link a connected account |
set_skill, set_knowledge | Propose a workspace skill or something Ahamo's AI should know about the app; it applies once someone confirms it in Ahamo |
Documentation
| Tool | What it does |
|---|---|
search_docs | Searches this documentation and returns up to 10 pages with a short passage each |
read_doc | Reads one page of this documentation |
Plans and limits
| Limit | Value |
|---|---|
| Calls | 120 a minute per person |
read_file | 2 MB |
query | One statement, 10 seconds, 500 rows |
upload_file | 10 MB, two at a time |
get_turn wait | Up to 50 seconds |
For agents that run on their own, see service credentials.
Troubleshooting
A changes tool is missing. The connection reads only. Reconnect with ?read_only=false and allow changes, or ask
your administrator whether your organisation allows changes.
A tool says production is read-only. Production changes only through publish.