Skip to main content
Genie is the platform-native assistant built into Noxus. It lives in the app itself — not on a separate page — and can both guide you through the product and operate the platform on your behalf: creating and editing flows, configuring agents, searching knowledge bases, querying tables, and running work in a sandbox. Unlike an agent that you build and deploy, Genie ships with Noxus and is pre-wired to work against your own workspace. Think of it as a co-worker who already knows the platform and has hands on the same tools you do.
Genie is currently in beta — the experience keeps improving. Availability is controlled per organization (see Enablement & permissions).

​
What Genie can do

Genie discovers the platform’s own tools through the Noxus MCP server and can act across the product:

Build & edit flows

Create workflows and edit them node by node, wiring configuration for you as you describe what you want.

Configure agents

Read and adjust agent setup — instructions, tools, knowledge — so you can stand up an assistant by conversation.

Search knowledge

Look things up across your knowledge bases to ground its answers and actions.

Work with tables

Query and reason over your workspace tables to answer data questions.

Run work in a sandbox

Use a persistent sandbox shell to process data, run scripts, and produce files.

Navigate the app

Guide you around the interface and take you to the right place for a task.
Genie also plans multi-step work with a todo list and can attach files to the conversation.

​
How Genie relates to agents and MCP

Genie is a special, hidden agent that Noxus provisions and manages for you. It reuses the same agent runtime, tools, and sandbox that power the agents you build — the difference is that Genie is created automatically, is scoped to help you operate Noxus, and is configured by the platform rather than in the agent builder. Its platform actions run through the Noxus MCP server — the same in-app tool surface the SDK exposes — bound to your workspace with your own permissions. So when Genie edits a flow or reads a knowledge base, it does so as you, subject to the same access rules.
Genie binds to the platform’s read and build tools for flows and keeps them scoped: it uses the flow editing and read tools, but destructive and bulk management operations (such as deleting or running flows outright) are deliberately left out of its toolset.

​
Sandbox & approvals

Genie’s sandbox is a persistent shell workspace — it stays available across the conversation so Genie can work step by step rather than one command at a time. Genie uses this shell for data and code work instead of one-shot code execution. Because the sandbox can write files and run commands, those actions are gated behind your approval:

Write approval

Genie asks before writing files in the sandbox.

Execute approval

Genie asks before running shell commands.
You stay in control — Genie proposes the step and you approve it before anything runs. As with any agent, running sandbox code also depends on the relevant platform permissions being granted.

​
Enablement & permissions

  • Organization-gated. Genie is enabled per organization. Where it isn’t enabled, the assistant surface won’t appear.
  • Managed by org admins. Organization administrators can open Settings → Genie to review and adjust Genie’s prompt, model, and tools, just like an agent’s configuration.
  • Acts as you. Genie operates with your workspace permissions — it can only reach flows, agents, knowledge bases, and tables that you can, and higher-risk actions (like sandbox execution) still require the corresponding permissions and your in-conversation approval.
Genie is a shared, tenant-managed assistant that lives in a hidden system workspace — it doesn’t appear in your normal agents list and isn’t edited from the agents page. Admins manage it from Settings → Genie.