Creytix Chat
Deterministic assistant and tools router with module context.
Note
Creytix Chat is part of Creytix Connect — the registry of self-hosted tools that replace the SaaS your agent-tooling stack usually rents.
Overview
Creytix Chat is the assistant surface built into your workspace — one place to ask for something in plain language and have it routed to the right tool. It knows which module you're working in, so a request made from Forge behaves differently than the same request made from Inspector, without you having to say so.
| Creytix tool | Replaces |
|---|---|
| Creytix Chat | Ad-hoc agent tool-routing SaaS |
Chat's routing is deterministic by design — requests map to fixed, known actions instead of an open-ended agent guessing at what tools might apply.
How it works
A request moves through three stages:
- Context sync — Chat picks up which module and workspace you're currently in.
- Deterministic routing — the request is matched to a fixed, known action rather than left to open-ended agent guessing.
- Handoff — if the request belongs to another module, Chat hands the thread to it (Forge, Inspector) instead of trying to fake the whole job itself.
Steps
- •
Open Chat from any module
Chat is available from wherever you're working in the Creytix Control Panel — it already knows the module and workspace context.
- •
Ask in plain language
Describe what you need. No special syntax or command list required.
- •
Let Chat route the request
Chat matches your request to a known action rather than improvising a tool call.
- •
Follow the handoff
If the work belongs in Forge or Inspector, follow the thread there — context carries over.
Capabilities
- Module-aware context — Chat knows what module and workspace you're working in without being told.
- Deterministic tool routing — requests map to fixed, known actions, not open-ended agent improvisation.
- Cross-module handoffs — a thread can hand off into Forge or Inspector so work continues where it belongs.
- Native to the workspace — built into Creytix, not a third-party agent-orchestration subscription.
Limits & honest scope
Creytix Chat trades some open-endedness for predictability — that's a deliberate choice, not a gap we're racing to close.
- Because routing is deterministic, Chat favors known, mapped actions over fully autonomous agent behavior. If you want a free-form agent that improvises novel tool calls, that's a different tradeoff than Chat makes.
- Handoffs currently cover the modules built to receive them (Forge, Inspector today); coverage grows as more modules wire in.
- Chat is built for working inside Creytix — it isn't a general-purpose chatbot builder for non-Creytix products.