Skip to content
Dashboard
Theme
Theme

What init and agent install read

The files ohauthcat init and ohauthcat agent install read and write, what they never read, and why no AI model sees your code.

View Markdown

ohauthcat init and ohauthcat agent install change files in your project, so here is exactly what they touch.

Neither command calls a language model. init plans its changes from fixed templates and pattern matching, and agent install writes fixed files. The only network calls are init’s callback registration and test sign-in through the management API. Your source code never leaves your machine through these commands.

  • The framework declaration: package.json and its lock files for Node, or pyproject.toml and requirements.txt for Python.
  • Whether conventional auth configuration files exist, such as firebase.json, supabase/config.toml or amplify_outputs.json. Their contents are never read.
  • The entry file of an Express TypeScript project and the Django settings and URL configuration, to find where to insert a block.
  • Any file it proposes to create that already exists, to show you the diff.
  • .env and every .env.* file except .env.template. If a proposed file would be one of these, init stops and shows only its proposed contents.
  • Package manifests and lock files are read for detection but never edited; init does not install packages.
  • Nothing outside the project directory.

It writes .env.template only when the project has none, with placeholders only. Every change is applied after your review, written atomically, and refused if the file changed after you reviewed it. The record in .ohauthcat/init-changes.json holds the original contents of files it changed, so keep it out of version control if those files are private.

  • An MCP server entry named ohauthcat in the editor’s MCP configuration. It refers to the OHAUTHCAT_API_KEY environment variable; the key itself is never written to any file.
  • A skill or rules file with the integration steps and the security rules.

Existing MCP configuration files are merged, keeping your other servers. Windsurf keeps MCP servers in a global file in your home directory (~/.codeium/windsurf/mcp_config.json), which is the only file written outside the project. See AI-assisted integration.