◔MUROAXO← Back to MuroAXO
PRODUCT / AI TRANSPARENCY

AI notice

Effective 7 November 2026 · MuroAXO is operated by Maykesh Saravanan and coordinates models and project tools. The model remains responsible for its own generated response.

Your selected provider receives your request

When you send a message, MuroAXO sends it and relevant selected project context to the provider and model configured in your session. If you attach an image, it is included in that request. If research is enabled, the provider's hosted search feature may be used. Check the provider's privacy terms and account controls before sending sensitive information.

Generated output needs review

AI can produce incorrect facts, broken code, insecure changes, outdated citations or content that does not fit your needs. Review generated code, dependencies, commands and research sources. Test changes in an environment you control before deployment. MuroAXO is an aid to your judgement, not a substitute for professional advice or security review.

Code execution

Code execution is opt-in and is available only when the selected provider/model supports its native tool. OpenAI Code Interpreter runs Python in an OpenAI-hosted sandbox; Anthropic Code Execution runs commands and file operations in an Anthropic-hosted sandbox; Gemini Code Execution runs Python in Google's managed environment. These environments are separate from the MuroAXO Worker and do not have direct access to your MuroAXO project files. Code and output are sent to the selected provider and provider charges may apply. Gemini 2.5 Pro, Flash and Flash-Lite run code without MuroAXO workspace tools in that request; supported Gemini 3 and 4 models can combine code execution with those tools. Compatible API gateways do not expose a standard code-execution tool. Availability, limits and billing depend on the provider, model and account.

Human control over project edits

MuroAXO's normal file-writing flow pauses to show proposed changes for approval. Auto apply is a separate setting that lets the model's workspace writes proceed without that per-change review. Provider-hosted code sandboxes remain separate from those project writes. You remain responsible for deciding whether to use these features and for checking resulting files.

Questions

For questions about MuroAXO's handling of prompts and workspace content, see the Privacy Notice or contact info@leanopsstudio.co.uk.

MuroAXO · Operated by Maykesh Saravanan
PrivacyTermsAcceptable useCookies & storage