Skip to main content

​
Agents

Under App Blueprint → Agents, GenieForge stores an operator within the application: instructions, tool access, guardrails, and chat branding for an audience. It is not only a chat persona. You describe how each audience should be helped and what they must never do; GenieForge configures agents to match. Find them under App Blueprint → Agents. Skills live under App Blueprint → Skills. The reserved System agent is the default for owner/admin portal chat and for builder Chat mode. Other end-user roles only get portal chat when you assign them an agent. Chat instructions, welcome, and memories for the default chat path live on App Blueprint → Agents → System. Open System to edit instructions (include any few-shot examples in that prompt), memories, and the welcome message shown when someone starts a new conversation in builder Chat mode or as owner/admin in the portal. Chat is always told which project the conversation is in (the project name). Tools, files, and data in that chat belong to that project only. Other projects of the same app keep their own data. You do not need to bake the workspace name into the agent’s instructions. Agent skills are domain modules you attach to an agent: instructions plus a tool list for that domain. When an agent has no skills attached, it can use every tool you have allowed for it. When skills are attached, tools that belong to inactive skills stay hidden until the skill is activated (or listed under Always on tools). Tools that are not tied to a skill stay visible. The System agent works the same way for owner and admin: it can use the full tool list until you attach skills. Attach skills when you want the agent to load a domain only when it is needed, instead of offering every tool every turn. Skills are part of the app blueprint (versioned like agents and tools). End users and Preview as → Published use the last published skill catalog and attachments. Preview as → Draft uses your live unpublished skills. Publish from the sidebar Publish page when draft skill work should reach customers. See Versions and rollback. Roles remain the security boundary. Skills never enlarge what a role already allows. Tables in Chat vs pages. Granting a role access to a table lets pages and named tools use that data. It does not automatically put the raw table in that role’s Chat toolbox. New custom agents keep raw table tools out of Chat. Existing agents and the System agent keep today’s bind-everything behavior until you change them. Open App Blueprint → Agents to see that agent’s table-tools setting. Ask the Building agent if a specific table should appear in Chat, or if Chat should stay on named wrappers only. For a pages-only audience (browse pages, no AI chat), create the role and do not assign an agent. The portal hides chat, My Chats, and My Memories for that role.

​
Where it lives

App Blueprint → Agents, plus role assignment under Access. The System agent is the default for owner/admin portal chat and builder Chat mode. Owner and admin still use that fallback when no other agent is selected. Page chatbots can host a specific agent even when the role has no portal-wide agent.
Attach a Billing skill to the support agent with the charge and refund tools. Keep those tools hidden until the skill is activated.

​
How to verify

  1. Open App Blueprint → Agents and confirm instructions, model, capabilities, skills, and Always on tools.
  2. Confirm which roles get that agent (other end-user roles only get portal chat when assigned an agent).
  3. Preview as each role. Confirm the wrong role cannot use staff-only tools.
  4. Re-check App Blueprint → Access after you attach a powerful tool.
A role with no agent gets a pages-only portal. Owner and admin use the System agent when no other agent is selected. An agent can serve more than one role. You can also place a specific agent in a page chatbot so a screen opens with the right operator already selected (page chatbots work even when the role has no portal agent).

​
Limits and notes

Optional memories can keep useful facts about a person across conversations. They are not a substitute for structured data; see Memories. Chat can show rich cards, tables, and stats. New agents inherit App Settings → UI Features → Rich Display (on by default). App Blueprint → Agents shows Rich Display as On, Off, or Inherit app setting. Ask the Building agent to turn rich display off for a text-only agent, or on if you want an explicit override. For a conversational agent (a page chatbot that should feel like talking to a person), you can hide chat chrome: the “Thinking for Xs” bubble, the always-on “Thinking…” line, and the credit count after a reply. Usage is still metered. Hide the credit count only on named staff or customer agents. The builder dashboard and the System agent (owner and admin) always show credits. Ask the Building agent to turn those chrome options off on the agent. Common mistakes: one agent for every role; expecting every role to chat via the System agent (only owner/admin keep that path; other roles need an agent); skipping Access review after adding a powerful tool; giving the portal agent Build-like powers in instructions.