Altostrat Studio is here — the AI-native network operations IDE for engineers running production. Terminal, diagrams, runbooks, and Copilot in one workspace. Get started →
Save structured facts you or Copilot want to recall later, and find anything in the workspace with one search box.
Memories are the facts you or Copilot want to recall later. “This site’s core switch is 10.12.0.1.” “This customer’s VPN requires IKEv1.” “After the last migration we had to flush ARP on the distribution pair.” The things that matter for next time, written down the moment they’re learned.Search is the other half. Studio indexes everything in the workspace — memories, hosts, diagrams, procedures, conversations, generated artifacts — so Mod+K finds what you need without you having to remember where it lived. You don’t browse; you search.Together, they make the workspace feel like it remembers. You stop re-deriving knowledge you already had.
Save facts that will change how someone works next time. A good memory is durable, scoped, and useful without the original chat.
Good memory
Better than
”Site HQ uses 10.12.0.1 as the core switch management address."
"HQ switch."
"Customer ACME still requires IKEv1 on the legacy VPN until migration ticket CHG-123 closes."
"VPN weird."
"BGP neighbor 192.0.2.7 flaps during provider maintenance; check carrier ticket before changing local config."
"BGP flap happened."
"Use procedure Check WAN failover before opening a vendor case for site MEL."
"Remember failover stuff.”
Do not save secrets as memories. Store secrets in Keychain and save only the operational hint, such as “use the shared firewall admin credential” or “the vendor portal uses the customer SSO account.”
Memories are categorized so Copilot can scope its recall when the conversation calls for it. The categories match how network knowledge usually organizes itself.
Category
Typical content
General
Anything that doesn’t fit a category.
Topology
Site layouts, uplinks, HA pairs.
Procedure
Methods that worked, sequences to remember.
Credential
Credential hints (never the secret itself — secrets live in Keychain).
Incident
Post-mortem facts, root causes, symptoms.
Config
Device-specific configuration notes.
On top of categories, every memory supports free-form tags — hq, bgp, maintenance-q1, a change ticket, a site code. Tags are the right tool for cross-cutting filtering that doesn’t belong in any single category.
There are three ways to save one, and you’ll use all of them:
From chat — ask Copilot to save something: “save this as a topology memory tagged hq” or “remember that this customer’s VPN requires IKEv1”.
Manually — open the memories activity in the sidebar and create one.
Automatically — Studio promotes high-value facts from conversations into draft memories you can keep or discard. The good ones usually come from a chat you’d have wanted to summarize anyway.
Memories are meant to persist. Delete one only when it’s wrong, obsolete, or explicitly no longer needed.
Mod+K opens the command palette. Type anything — a hostname, a phrase, an IP — and results come back grouped by kind: hosts, diagrams, procedures, conversations, memories, artifacts, commands. Mod+Shift+P biases toward commands, which is the right choice when you want a navigation target rather than content.Studio searches meaning, not just words. A search for “border router” can surface devices tagged edge or with names like core-gw-01. A search for “power outage last Tuesday” can surface the incident memory that captured it. You don’t have to remember the exact phrase you used when you wrote it down.Use search before creating something new. If a procedure, host, or memory already exists, opening it first keeps the workspace clean and gives Copilot better context than starting a duplicate.
Alongside search, Copilot maintains a knowledge graph of how things relate — an IP belongs to a subnet, a subnet belongs to a site, a device speaks to a neighbor, a procedure was run against a host, a memory was extracted from a conversation. When you ask Copilot something, it uses these relationships to scope the answer to the right part of the workspace.You don’t configure the graph. It’s maintained continuously from your inventory and the work you do around it.
For hard questions — the ones where the answer isn’t in any single memory or object — Copilot blends semantic search and graph traversal to assemble context before replying. You see the same conversation, but the retrieval under the hood is the reason the answer fits.
