Skip to content

Security: ronmiz/infernoflow

Security

SECURITY.md

Security & Privacy

infernoflow stores AI session memory locally as plain JSONL files. As of v0.43.6, it does not make any network calls in any default command path. This document describes exactly what runs on your machine, and how to report security issues.

What infernoflow writes to disk

When you run infernoflow init or infernoflow log, the tool writes plain text/JSON files in your project:

  • .ai-memory/sessions.jsonl — one entry per line, each ~200 bytes. AMP-format JSON. Holds the gotchas/decisions/attempts you've logged.
  • .ai-memory/amp.json — project metadata (name, AMP version, simple config).
  • .ai-memory/handoff.md — generated by infernoflow switch. A markdown handoff for AI agents.
  • .cursorrules, CLAUDE.md, .github/copilot-instructions.md — auto-injected sections wrapped in <!-- infernoflow:start --> / <!-- infernoflow:end --> comment markers. Your manual edits outside those markers are never touched.

The tool never writes outside the project directory it's run from. It never modifies system files, registry entries, or shell profiles.

What infernoflow runs at install time

Nothing. No postinstall script. npm install -g infernoflow only copies files into node_modules — no code executes.

What infernoflow sends over the network

Nothing by default. infernoflow is fully local-first. One opt-in feature can send data:

AI provider commands (infernoflow ai setup, infernoflow explain, etc.)

If you configure an AI provider via infernoflow ai setup, certain commands send your code/context to that provider (Anthropic, OpenAI, Google, OpenRouter, or local Ollama). Same trust model as using the provider directly. Off by default — you must explicitly run infernoflow ai setup.

The MCP server (templates/cursor/inferno-mcp-server.mjs) runs locally as a subprocess of your AI tool (Cursor / Claude Code / etc.). It only invokes the local infernoflow CLI — no direct network calls. Your AI tool's own network behavior is unchanged.

What was removed in v0.43.6

  • Cloud sync (Supabase mirror of session memory) — alpha auth model that wasn't a real security boundary
  • infernoflow login / logout / whoami — cloud-only, no purpose without sync
  • infernoflow dashboard (local web server on :7337) — duplicated the VS Code sidebar

Removed code is preserved in legacy/ for git history and potential revival as separate packages.

What infernoflow does NOT do

  • No telemetry. No analytics, no error reporting, no install-tracking pings.
  • No auto-updates. The CLI never modifies itself; updates only via npm install -g infernoflow@latest.
  • No background processes. Nothing daemonizes; commands exit when done.
  • No reading of files outside your project. Glob patterns are scoped to the working directory.
  • No cloud sync. Removed in v0.43.6. Local-first only.

Reporting security issues

If you find a vulnerability, please report it privately:

Please don't open a public issue for security bugs. We'll acknowledge within 72 hours.

There aren't any published security advisories