slaunt
DOCUMENTATION

Provider tools

When a workspace connects providers like Slack or Notion, their tools show up in tools/list alongside Slaunt's own, under the provider's namespace. Calls go through Slaunt Gateway rather than straight to the provider, which is what applies workspace policy, spend caps and audit, and keeps provider credentials away from the agent.

Discovery status

If provider tools are missing, tools/list says why in _meta:

{ "tools": ["..."], "_meta": { "ai.slaunt/gateway-discovery": { "status": "available", "tool_count": 12 } } }
statusMeaning
availableProvider tools are listed
unavailableDiscovery failed; code gives the reason
disabledGateway is off for this server
not_configuredGateway isn't set up

Calling them

Provider calls need a bound thread, so call thread_begin first. Gateway attributes each call to the agent from that thread binding; any agent ID passed in arguments is ignored. Calling run_begin too gives Quaero a task description; otherwise a minimal run is started automatically.

When entitlements, connections or policies change, the server sends notifications/tools/list_changed on the notification stream. Refresh tools/list when it arrives.