Commander
Commander is Norbital's built-in natural-language workspace assistant. It can help you explore the workspace, retrieve records and metadata, navigate to the right screen, and stage configuration work in a blueprint fork.
Two Main Modes
From a configurator's point of view, Commander has two main jobs:
- Agent chat for questions, retrieval, analysis, and configuration work
- Navigation for jumping to apps, pages, system modules, and settings
Draft Forks
When you ask Commander to change configuration, it does not edit production directly. It works in a fork-backed draft context so you can review the staged result first.
What Commander Can Do
- answer questions about collections, fields, and configuration,
- retrieve records and summarize what they show,
- navigate you to relevant pages or modules,
- draft configuration changes in a fork,
- run bounded code-based analysis when needed.
Fork Ownership Lock
Configuration work still respects fork ownership. If another user owns the relevant fork, Commander can hit the same lock constraints you would see in the manual UI.
When Commander finishes configuration work, the fork lock should be returned so a human can review, test, and merge the result.
Example Prompts
Good prompts are concrete and outcome-oriented.
- "Show me all projects created this week that are marked urgent."
- "What fields exist on the Suppliers collection?"
- "Add a new collection called Suppliers with status and owner."
- "Grant the Sales team view access to Invoices."
- "Create a dashboard page in the Operations app."
- "Take me to approval settings."
Best Practices
- Use precise nouns such as collection names, team names, or route names.
- Expect clarification when a request could be implemented in more than one way.
- Review staged fork changes before merging, even when Commander created them.
- Use Commander to accelerate setup, not to bypass governance.