Cortex — Hierarchical Context
How Waykee Cortex automatically builds the right context for every robot, inheriting knowledge level by level.
Objects come in two flavors: Knowledge Objects (systems, modules, screens/programs — the permanent documentation of what exists) and Task Objects (tickets, milestones, projects — the work being done). Both live in hierarchies, and children automatically inherit the context of all their ancestors.
💡 The node names are fully customizable. "System", "Module", "Screen/Program" are the default labels for software teams — but any industry can define its own hierarchy. The examples below show a software team and an education institution using the same engine with different node names.
When a robot opens the ticket "Add Recurring Invoice toggle", it automatically receives the documentation of all four levels: the Atlas ERP platform overview, the Finance Module workflow rules, the Invoice Entry Screen/Program specifications, and the ticket itself. No manual context-passing needed.
A task links to both a Knowledge hierarchy (what screen/system it belongs to) and a Project hierarchy (what milestone/project it's part of). The robot receives context from both sides.
Each robot has a personality (system message) and a set of Instruction Packs (similar to skills) — reusable knowledge bundles assigned by the owner. Some packs are shared across robots; others are unique to one.
A robot in Waykee can be a simple API call to any model (GPT, Gemini, Claude API…), or a full agentic worker powered by Waykee Worker — an open-source wrapper around Claude Code, Codex, and coming soon Cursor and others. When using Waykee Worker with Claude Code, your existing Claude Code subscription is reused — no extra model cost.
Every time a robot is summoned on a Waykee, it receives a complete, structured prefix before any conversation begins. This prefix is assembled automatically from three layers — giving just the right context, so the robot wastes zero time figuring out where it is or how things work.
The robot is summoned. Before processing any message, the system assembles the complete context prefix.
It knows the full platform, the finance rules, the exact screen it's working on, and the precise task to accomplish. This prefix is reused for the entire conversation, keeping every response in context.
Any waykee — a task, a screen, a project — can have subscribers: people and robots who are part of that conversation. Everyone sees the same thread, each contributing from their role.
Those tools are great at tracking work — and yes, you can connect an AI bot to them via API so it reads the ticket and posts a comment. But what does that bot actually know? It sees the ticket title, the description, maybe the comments. That's it.
It doesn't know what screen the ticket belongs to, what module it lives in, what coding conventions your team follows, or what was decided in that related meeting last week. Every session starts from zero. Waykee's difference isn't that bots can participate — it's the depth of what they receive when they do.
It's not just tickets. Every object in the hierarchy — a System, a Module, a Screen, a Project, a Milestone — has its own persistent chat thread. Teams can discuss architecture decisions at the System level, design choices at the Screen level, or sprint blockers at the Milestone level, all in the right place.
Waykee Cortex doesn't just give robots context — it also keeps humans in control. Every token spent, every secret used, every action taken leaves a permanent, auditable trail.
Waykee Cortex was built for organizations that need to trust their AI agents — not just watch them. Token budgets, secret isolation, and full audit trails are built into the platform, not bolted on afterwards.
The full Waykee experience is available on iOS and Android — so your team stays connected to their tasks, robots, and conversations from anywhere.
WaykeeMobile is built with .NET MAUI — a single codebase that runs natively on iPhone and Android. Browse your object hierarchy, open tickets, chat with robots, and review audit trails on the go.
Get notified the moment a robot completes a task, a teammate adds a comment, or a ticket changes status — without having to poll the app.
Record voice notes directly from the mobile app and attach them to any ticket. Perfect for quick feedback, field observations, or hands-free status updates — transcribed automatically by the robot if needed.
Define multi-step workflows that run automatically on a schedule or trigger. Recurring tasks that repeat, delegate, and report — all within the Waykee hierarchy.
Waykee Cortex will be released as open source in the coming days. Register now and we'll send you a notification the moment the repository goes live.