Understand Cogitave Massar
Cogitave Massar is the guardian remote-console agent that gives an authorized operator a terminal on a customer device without opening an inbound port or requiring a VPN. This module explains what Massar is and the one job its agent performs, why an outbound-only connection model removes the need for inbound access, how a session moves control messages and terminal bytes across the agent-broker-operator chain, and how a device authenticates while Diyar-side RBAC and audit authorize and record who connects. It also states plainly which parts are shipped today - the CLI installers with a static per-device token, Windows and Linux support - and which are still previews, such as the graphical enrollment wizard and macOS support.
By the end of this module, you will be able to:
- Explain what Massar is and the one job its agent performs: dial out, bridge a PTY, hold no standing shell.
- Explain why an outbound-only connection model removes the need for an inbound port or a VPN.
- Describe the three parties in a session and how control messages (Text frames) are distinguished from terminal bytes (Binary frames) on the wire.
- Describe how a device authenticates with a per-device token and how an operator is authorized and audited on the Diyar side.
- State accurately which install and enrollment paths are shipped today, and which are previews.
Prerequisites
- No prior Cogitave product experience required.
- Familiarity with basic terminal/shell concepts and how a WebSocket connection works is helpful but not required.
Units
- 01Introduction4 min
- 02Why dial out: no inbound port, no VPN5 min
- 03How a session works: agent, broker, and the PTY bridge7 min
- 04The security and consent model7 min
- 05Knowledge check4 min
- 06Summary3 min
Related
- Install and operate the Massar agent This module installs and operates the Cogitave Massar agent: the small, cross-platform binary a customer runs on a device so an authorized Diyar operator can dial in for an audited remote terminal, with no inbound port and no VPN. You install it with the CLI installer for your OS - install.sh on Linux, install.ps1 on Windows - confirm it is verified and running as a service, trace a session from open to close, reproduce the whole relay locally with the project's own dev harness, and remove it cleanly when you are done. Two facts are stated plainly rather than glossed over: today's supported install targets are Windows and Linux only, and every end-to-end proof described here is the local dev harness, not a production Diyar deployment.
- Glossary The terms used across Cogitave documentation and training, defined once - agent kernel, capability grant, provider driver, sandbox, sovereign unikernel, MCP, evidence, and the words that are easy to assume.
- What Namzu is Namzu is an agent kernel for TypeScript, not an application framework. What that distinction buys you, what the kernel owns, what it deliberately refuses to own, and how the layering keeps your stack yours.