Working with the Terminal

What is the Terminal

The Terminal is the conversational interface for asking questions and running work in natural language — available everywhere you work. You're not filling out forms or clicking through menus, and you don't need a well-formed prompt: just tell Terminal the work you want done, and it goes to work.

This isn't a search box. Terminal returns an answer, grounded in your Workspace's data first — your records, your files, your team's past work — combined with curated external sources where relevant. And it's not a one-shot answer: build on the conversation to refine it, dig deeper, and chain steps together into real work. This is the entry point to everything the platform knows and does.

Chat tools help individuals generate answers. NetworkOS helps organizations build intelligence.

Sources

Every answer Terminal gives cites its sources, so you can trust the information presented. Each source shows you exactly what informed the answer — a record, a file, a Data Pack, or a website.

Where a source is something you can open, you can: click through to the record or the website behind it. A Data Pack source isn't a separate place to browse — it names which curated dataset informed the answer, without a page behind it to click into.

Slash commands

Where to find it: type / in Terminal to open the command menu.

The command menu lists every Agent Skill available to your Workspace — catalogue and managed — that you can invoke directly. Typing a skill's slash command runs that skill on your request immediately, rather than leaving it to Terminal to decide whether to use it.

For what each Agent Skill actually does, see Agent Skills.

Saving and sharing your work

Anything you generate in Terminal — a conversation, a research run, a summary — is private to you by default.

Expand an output into Studio to review and refine it before you save it. From there, save it to:

• Your Workspace — visible and buildable-on by your whole team.
• A Mission — scoped to that specific thread of work.

Saved items — whichever way you saved them — show up in the Artifacts navigation, so there's one place to find anything your team has kept.

Your conversation history

Conversations in Terminal — along with their outputs and answers — are private to you. The only way something becomes visible to your team is if you save an output as an artifact to the Workspace; the conversation itself stays yours.

Where to find it: the clock icon at the top of the chat.

From your conversation history, you can:

• Revisit and jump back into any past thread, including its outputs
• Rename a conversation
• Delete a conversation

Warning: deleting a conversation removes it, including any unsaved outputs inside it, and can't be undone. Anything you've already saved as an artifact to a Workspace or Mission is unaffected.

Long conversations are automatically summarized and compacted along the way, so your work isn't interrupted as the thread grows.

Bringing context into Terminal

Sometimes you want Terminal working with something exact, not just what it can find on its own.

Mentions

Type @ in Terminal to pull up the lookup and bring an exact record, artifact, or file into the chat directly. Use a mention whenever you want to reference something precisely — it sharpens the answer, since Terminal is working from the specific thing you pointed to instead of guessing from a description.

Uploading a file

Attach a file directly into a conversation to give Terminal something specific to work from. Like the conversation itself, an uploaded file here is private to you and only lives in that conversation — it doesn't add anything to your Workspace's data.

If you save an output from that conversation as an artifact, the file is preserved as one of its sources. If you don't save the output, the file doesn't persist anywhere.