AI and connected agents
How built-in local AI, review, and optional bring-your-own-agent connections differ.
Local AI: always local, always reviewable, always optional
Chronal Studio’s built-in AI can suggest dated facts, events, knowledge, causes, and effects from your writing. The model runs on your device. Its output is a proposal, not an approved project fact.
- You write normally.
- If local AI is enabled, it may suggest information to track.
- Chronal checks the suggestion for errors.
- You accept, revise, or reject it.
- Only something you accept becomes part of the project’s tracked record.
Studio remains useful without model files, special graphics hardware, or AI assistance.
Bring your own agent, if you want
Model Context Protocol (MCP) is a standard way for an AI agent to use another application’s tools. Chronal can provide a connected agent with Engine-backed operations for reading, questioning, and changing a project, so the agent does not need to guess how Chronal’s files work.
Chronal Settings provides guided setup for Codex and Claude Desktop. Other compatible agents can be configured manually. The connection is optional, can be removed later, and is not required for any core Studio workflow.
A connected outside agent is different from Chronal’s built-in local AI. The agent may use a cloud model and may send project content to its own provider. Review that product’s privacy terms and settings before connecting it.
Command-line access
The command-line interface (CLI) is a separate terminal tool for scripts and advanced automation. Like MCP access, it uses Chronal Engine and is optional.