Model & settings
Any chat model enabled for your tenant, or the tenant default. Tune reasoning effort and verbosity where the model supports them — and swap models from a dropdown.
An agent is a versioned prompt, an approved model, scoped knowledge and exactly the tools IT grants it. Assemble one in minutes — or describe the outcome in plain English and review the blueprint the AI Agent Builder drafts for you.
Builders assemble agents from components IT has already approved. Nothing is granted by default — not a model, not a folder, not a tool.
Any chat model enabled for your tenant, or the tenant default. Tune reasoning effort and verbosity where the model supports them — and swap models from a dropdown.
A saved prompt from the central library, with variables, logic and reusable fragments — optionally pinned to a specific version.
Only the knowledge folders and websites you select. Per-site limits of 1–20 results and a minimum relevance score from 0 to 1 filter weak matches before the model sees them.
Per-server, per-tool checkboxes. An agent gets exactly the tools an admin grants — never a whole server by accident.
Where the model supports them: OpenAI web search (domain-restricted) and file search; Anthropic web search, web fetch and code execution.
Set tool choice to auto, required or none, and cap how many tool steps a single reply may take.
Run an agent on a cron schedule with friendly presets — for digests, checks and proactive outreach.
Attach published workflows to when a conversation starts, a message arrives or a conversation closes — blocking the reply or in the background.
Deploy the same agent to web embeds, Teams, Slack, phone lines and the API without rebuilding it per channel.
Keep voice and policy consistent across every agent and AI workflow step. Prompts live in one organised library, with full version history — so you always know what changed, who changed it, and which version produced a given answer.
Describe the problem in plain English, typed or spoken. The builder asks clarifying questions — or uses sensible assumptions — then drafts a complete, editable blueprint. Nothing is created until you approve it.
Agents stream their replies, call tools in parallel and cite what they used. Controls apply before the model is ever called.
Every agent run is stored with a full, ordered trace — from the input, through each model call and tool call, to the outcome. Runs link to their conversation and back.
Distributed building only works when access is precise. Gecko lets you delegate to teams while IT keeps the institution-wide view.
Agents record who created them, and list pages filter between “Mine” and “All” — so teams find their own work quickly.
Custom roles can be limited to specific agents, websites or workflows. Run is separate from write — people can operate an agent they can’t edit.
Every create, update and delete is recorded against the person or API key responsible.
Change the AI model behind a live agent from a dropdown. Every answer shows its sources. Every run shows every step.
With managed implementation, Gecko helps define the use case, connect knowledge and tools, set the controls and support go-live.