How it works: the graph project
A TeraBrain NX project is a set of nodes connected in two ways. Only agents reason: every other node brings conversations to agents or gives them tools.
Agents, channels, data, code and integrations are described together, in a versioned project.
Visual editor, natural-language Builder or external assistant: the result is the same project.
Two kinds of link
- Tools. One node provides tools and another uses them. A database provides
query, an agent uses it. - Conversations. One node starts conversations and another answers. A Telegram bot starts them, an agent answers.
- Web app
- Telegram
- Mailbox
- Voice
- Scheduler
- MCP server
- Instructions
- Model
- Database
- File storage
- Skill library
- Connector
- Sandbox
- Remote MCP
- Other agents
Two rules to remember: a conversation always ends at an agent, and a phone call reaches an agent only through a Voice node.
Nodes and ports
Every node has a type and four families of ports, with the labels you see in the console.
| Family | Console label | Meaning | Examples |
|---|---|---|---|
| exposes | Provides tools | The node provides tools | rw, ro, admin, functions, developer |
| consumes | Uses tools | The node receives tools | tools |
| sources | Starts conversations | The node starts conversations | delegate, handoff, agent, inbound |
| sinks | Answers | The node receives conversations | sink ("Conversations"), calls |
Versions and rollback
- Every change, from the editor, Builder or an external assistant, produces a new version recorded under the name of whoever made it.
- A change based on an outdated version is rejected, so as not to overwrite someone else's work.
- Rollback returns the project to a previous version. Beyond the point where a node with data was added, an explicit confirmation is required.
- Save rebuilds only the changed nodes; the rest keeps running.
The console map
| Area | Sections | What they are for |
|---|---|---|
| Build | Build, Graphs, Code, Skills, Files, Databases, Docs | Designing and developing: Builder, project list, code workspaces, libraries, files, databases |
| Run | Agents, Apps, Calls, Scheduled tasks, Logs | Using and observing: chats with agents, published apps, calls, scheduled tasks, logs |
| Organization | Settings, Members, Secrets, Variables, Connections, Identity, Sites | Administering: models, people, credentials, enterprise sign-in, machines |
Related pages
How to create a new agent
Step by step: project, agent node, instructions, model, tools, channel, testing and publishing.
Channels: how people reach agents
Web app, Telegram, mailbox, phone, scheduler and MCP server: how they connect and how you control who can use them.
Security
Roles, groups, credentials, enterprise sign-in and least privilege: how to protect an agent system.
Have an agent to take to production?Let’s talk.
We show you TeraBrain NX on your case: systems to connect, access and controls.