Skip to main content
The CLAUDE.md file (and its Codex equivalent AGENTS.md) is a special configuration file that tells your agent how to behave in this project. Coddo includes a built-in editor so you can manage it without leaving the app.

​
What is CLAUDE.md / AGENTS.md?

CLAUDE.md is a markdown file at the root of your project that gives Claude Code project-specific instructions. AGENTS.md plays the same role for Codex. Both are read by the agent every time it starts a session.
Coddo’s project-init flow generates both files and keeps them in sync. Edits made in the built-in editor write to whichever file your active provider expects.
Common things to include:
  • Project structure - Describe your file organization
  • Tech stack - List frameworks, libraries, and tools
  • Conventions - Coding style, naming patterns, file naming
  • Build commands - How to build, test, and run the project
  • Important rules - Things Claude should always or never do

​
Using the editor

  1. Click the CLAUDE.md icon in the sidebar
  2. The editor opens as a full-screen overlay
  3. Edit the markdown content
  4. Changes are saved directly to the CLAUDE.md file in your project root
A well-written CLAUDE.md / AGENTS.md dramatically improves your agent’s output quality. The more context you give, the better the results.

​
Generate with AI

If you don’t have a CLAUDE.md or AGENTS.md file yet, or if you want to start fresh, click the Regenerate button. Coddo will analyze your project’s codebase and automatically generate complete instruction files tailored to your project — including the tech stack, file structure, conventions, and build commands. This is the fastest way to initialize your project configuration.

​
Example CLAUDE.md

# My Project

## Stack
- React 19 + TypeScript
- Tailwind CSS v4
- Zustand for state management

## Commands
- `npm run dev` - Start dev server
- `npm run build` - Production build
- `npm run test` - Run tests

## Conventions
- Use functional components with hooks
- Name components in PascalCase
- Use kebab-case for file names
- Always add TypeScript types

## Rules
- Never use `any` type
- Always handle errors with try/catch
- Write tests for new features

​
Tips

  • Keep it concise — the agent reads the entire file for every session
  • Focus on what’s unique to your project
  • Update it as your project evolves
  • Include examples of patterns you want Claude to follow