KAEL Capabilities
This page separates implemented KAEL behavior from roadmap items.
| Field | Value |
|---|---|
| Product maturity | Live / evolving |
| Documentation status | Active |
| Last source review | 2026-06-26 |
| Changelog | KAEL Changelog |
Implemented public capabilities
- Non-streaming and Server-Sent Events chat.
- Model catalog discovery.
- Anonymous and authenticated sessions.
- Recent conversational history.
- Key/value user memory.
- AeThex knowledge matching.
- Identity and profile summaries.
- Feedback ratings.
- Featured and activity feeds.
- Generated-document creation and storage.
- Email one-time-code and AeThex OAuth-style sign-in flows where configured.
- Image-aware requests through a compatible model tier.
Implemented integrations
- Discord interaction verification and slash-command handling.
- AeThex service-status checks.
- Signed deployment webhooks.
- Optional Telegram bot initialization.
- Optional transcription and text-to-speech routes.
- DB-backed scheduled tasks and daily briefs.
- Tenant-specific prompts, knowledge, models, and rate limits.
Permissioned capabilities
Depending on clearance and operator authorization, KAEL can expose tools for:
- Live web retrieval.
- AeThex service checks.
- Passport and ecosystem lookup.
- Persistent world-model reads and writes.
- Observations and operator context.
- Agent execution.
- Deployment actions.
- Tenant administration.
Warning
The existence of a server route does not make it a public API. Operator and owner routes require explicit authorization and are intentionally excluded from public client examples.
Capability boundaries
KAEL does not guarantee:
- That every provider model is always enabled.
- That a public user has access to every tool.
- That experimental endpoints remain stable.
- That generated answers are authoritative without a linked source.
- That an available hostname means every feature is production-ready.
Client guidance
- Discover models using
/kael/models. - Treat clearance as server-calculated.
- Expect rate-limit events inside an SSE response.
- Store no operator token in browser code.
- Keep session IDs unguessable when they protect anonymous continuity.
- Provide users a way to inspect and clear memory.
Roadmap
Planned work belongs in KAEL Roadmap. Shipped behavior belongs here and in KAEL Changelog.