Namzu
9 entries tagged product Namzu.
- Agent platform fundamentals Start where you can build: install the Namzu agent kernel, register a model provider, make your first call, and declare a tool with an explicit authority. Then step down a layer to Yuva, the sovereign kernel Cogitave is building to enforce those declarations on hardware it controls - including an honest account of what Yuva cannot do yet.
- Build your first agent with Namzu Install the Namzu kernel, register a provider, make your first model call, and declare a tool with a typed schema and an explicit authority - locally, with no account.
- Agent identity and capabilities Every Cogitave agent acts under its own identity inside an explicit least-privilege capability grant, in a sandbox, with every action recorded as evidence. What that model guarantees, and where a human is still required.
- Check your environment Use the namzu operator CLI to verify a machine before debugging an agent - runtime version, installed packages, and whether the provider you registered is actually reachable.
- Choose a provider The model providers Namzu ships as drivers, how to register one, what changes when you switch, and which to pick for local development, hosted inference, aggregation, or an OpenAI-compatible endpoint of your own.
- 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.
- Packages reference Every published Namzu package and what it is responsible for - the kernel, the sandbox and telemetry layers, the operator CLI, the file registry contracts, and the eight model provider drivers.
- Quickstart - run your first agent Install the Namzu kernel and one provider, send a first message, and see the shape of a response. Local-first with Ollama, no account and no hosted service required.
- 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.
Other products