# Frame > Connect specs, decisions, and project knowledge so you and your AI build with shared understanding. Frame is a free, open-source desktop IDE for AI coding agents. Write a spec once and it becomes the plan your agents follow and durable project context that survives every session. Built on Claude Code; works with Codex CLI. - Website: https://frame.cool - Source (Apache-2.0): https://github.com/kaanozhan/Frame - Download (macOS, Windows, Linux): https://github.com/kaanozhan/Frame/releases/latest - Current version: 2.8.2 - [Project management beta waitlist](https://frame.cool/#waitlist): We’re building a project management layer for Frame. Join the beta waitlist to hear when access opens. Key facts: - `.frame/AGENTS.md`: Project rules and instructions. The AI reads this automatically. - `.frame/STRUCTURE.json`: Module map with an intentIndex, so agents jump straight to the right file. - `.frame/PROJECT_NOTES.md`: Architectural decisions and the context behind them, kept across sessions. - `.frame/tasks.json`: Tasks with status, context and acceptance criteria. - `.claude/rules/frame.md`: A synced copy of AGENTS.md that Claude Code loads at session start. The only file Frame writes outside .frame/. - Spec workflow: spec.md (/spec.new) → plan.md (/spec.plan) → tasks.md (/spec.tasks) → outcome.md (/spec.implement) - Supported AI tools: Claude Code, Codex CLI ## Docs - [Full description](https://frame.cool/llms-full.txt): everything on the site as plain text - [README](https://github.com/kaanozhan/Frame#readme): installation, usage, architecture ## Guides and articles - [How a Spec Becomes Lasting Project Context](https://frame.cool/blog/spec-driven-context): Follow an email-reminder feature from spec to outcome, and see how the same files guide implementation and give the next AI session useful context. - [Software development has changed. Your tools haven't.](https://frame.cool/blog/software-development-has-changed): A field note from the other side of the paradigm shift. Most dev tools were built for a workflow that has quietly ended. Here's what the post-paradigm platform looks like — built for agents first, humans second. - [Shared Project Context for Claude Code and Codex CLI](https://frame.cool/blog/multi-ai-support): How Frame gives Claude Code and Codex CLI a shared source of project instructions, specs and outcomes without maintaining two sets of context. - [Frame Server — Running Your IDE in the Browser](https://frame.cool/blog/frame-server): The distinction between Frame’s desktop application, the interactive website sample and the work toward a browser-based Frame Server. - [Why Frame? Building a Terminal-First IDE for AI Coding](https://frame.cool/blog/why-frame): Why Frame brings terminal sessions, spec-driven development and durable project context into one workspace for Claude Code and Codex CLI. - [Context Preservation — Stop Losing Decisions Between AI Sessions](https://frame.cool/blog/context-preservation): How Frame combines project rules, decisions and the spec → plan → tasks → outcome workflow to preserve useful context between AI coding sessions. ## Optional - [Releases](https://github.com/kaanozhan/Frame/releases): changelog and downloads for every version