Skip to main content

Forge and Guide: Coginiti's AI assistants explained

Coginiti's chat panel is powered by one of two agents, chosen automatically by your role and edition: Forge, the admin/user assistant, and Guide, the consumer assistant. This page explains what each one can do, why they differ, and how the agent decides what it's allowed to act on.

Background​

Coginiti serves people with very different jobs against the same platform: developers writing CoginitiScript against raw schemas, analysts exploring the catalog, and business consumers who just want an answer in plain language. A single assistant can't safely serve all three - a consumer shouldn't see raw schemas or table names, and a developer needs direct database and catalog access that a consumer should never have. Rather than one assistant with configurable limits, Coginiti ships two purpose-built agents and assigns the right one automatically.

Forge: the admin/user assistant​

Forge is available to every non-Consumer role (User, Admin) and to all Pro users. It has broad, mostly read-only access to your workspace, with approval required before it changes anything:

  • Catalog: search, list, and get item details - read-only browsing of the Project Hub
  • Catalog changes: create a project, create an item, delete an item - Forge asks for approval every time
  • Database: list connections, get schema
  • Semantic layer: list layers, get metadata, run a query
  • Documentation search: Team and Enterprise editions only
  • Web search and fetch
  • Draws Mermaid diagrams and asks clarifying questions when your request is ambiguous

Pro Forge has a narrower tool set than Team/Enterprise Forge: it lacks semantic layer tools and documentation search, since those features don't exist in Pro.

Guide: the consumer assistant​

Guide is automatically assigned to the Consumer role on Team and Enterprise editions - there's no Pro equivalent, since Pro has no Consumer role. It answers in plain language, grounded entirely in the semantic layer:

  • Tools: list semantic layers, get metadata, run a semantic query, web search and fetch
  • Refuses: writing raw SQL, exposing schema details, making catalog changes

Consumers open a new chat tab with Alt+T (Option+T on macOS) - a shortcut unique to the Consumer role, since Consumers don't work across multiple SQL editor tabs the way Forge users do.

Forge vs. Guide, side by side​

ForgeGuide
Who gets itUser and Admin roles; all Pro usersConsumer role (Team/Enterprise only)
Catalog browsingYesNo
Catalog changesCreate/delete, with approval each timeNo
Database schema accessYesNo
Raw SQLYesRefused
Semantic layer queriesYes (not in Pro)Yes
Documentation searchTeam/Enterprise onlyNo
Web search and fetchYesYes

Guide is deliberately limited to the semantic layer because that's the one layer of your data designed to be safe and meaningful for a non-technical audience: it exposes business names and metrics instead of raw tables, so a consumer question can be answered accurately without ever touching schema internals. Forge's broader access assumes a technical audience that already has permission to see the underlying database and catalog.

What admins should expect when assigning roles: changing a user's role to Consumer switches their assistant from Forge to Guide and narrows their chat access to the semantic layer, regardless of what database or catalog permissions they previously had. This change is irreversible - a Consumer can't be upgraded back to User or Admin, so they can't be handed Forge later.
See How to Set Up a Consumer with a Semantic Connection and AI Access for the full role-assignment walkthrough, including what a Consumer conversion deletes and how to undo a mistaken conversion by creating a new account instead.

How agent approvals work​

Whether you're using Forge or Guide, the agent asks before taking any action that changes state - creating a catalog item, deleting one, or anything else outside read-only browsing and querying. You'll see a prompt with three choices:

  • Allow - approve this one action
  • Allow per session - approve this type of action for the rest of the current chat session
  • Deny - reject the action; the agent will look for another way to help, or ask what you'd like instead

If a model call itself fails - a timeout or a provider error, for example - the agent retries automatically, up to three times, before reporting the failure back to you.


For the click-through mechanics of approving or rejecting an action in the chat panel, see Using the AI chat.

See AI in Coginiti Overview for the full map of AI features across the product.

See AI Roles and Editions Reference for the complete role and edition breakdown, including sharing, documentation search, and provider availability.


tip

For more information about other exciting Coginiti features visit our documentation

Thank you for choosing us!​