Ai Code Interface.El

[[file:./icon.png]]

• AI Code Interface

[[https://melpa.org/#/ai-code][https://melpa.org/packages/ai-code-badge.svg]] [[https://stable.melpa.org/#/ai-code][https://stable.melpa.org/packages/ai-code-badge.svg]] [[https://github.com/tninja/ai-code-interface.el/graphs/contributors][https://img.shields.io/github/contributors/tninja/ai-code-interface.el.svg]] [[https://github.com/RoggeOhta/awesome-codex-cli][https://awesome.re/mentioned-badge.svg]]

An Emacs interface for AI-assisted software development. The purpose is to provide a uniform interface and experience for different AI backends, with context-aware AI coding actions, and integrating seamlessly with AI-driven agile development workflows.

• Currently it supports these AI coding CLIs:

  • [[https://github.com/openai/codex][OpenAI Codex]]
  • [[https://docs.github.com/en/copilot/how-tos/use-copilot-agents/use-copilot-cli][GitHub Copilot CLI]]
  • [[https://github.com/google-gemini/gemini-cli][Gemini CLI]]
  • [[https://github.com/anthropics/claude-code][Claude Code]]
  • [[https://opencode.ai/][Opencode]]
  • [[https://grokcli.io/][Grok CLI]]
  • [[https://docs.cursor.com/en/cli][Cursor CLI]]
  • [[https://kiro.dev/cli/][Kiro CLI]]
  • [[https://cnb.cool/codebuddy/codebuddy-code][CodeBuddy Code CLI]]
  • [[https://aider.chat/][Aider CLI]]

• It also supports external backend packages:

  • [[https://eca.dev/][ECA (Editor Code Assistant)]] ([[./ai-code-eca.el][ai-code-eca.el]])
  • [[https://github.com/xenodium/agent-shell][agent-shell]] ([[https://github.com/xenodium/acp.el][acp.el]])
  • [[https://github.com/manzaltu/claude-code-ide.el][claude-code-ide.el]]
  • [[https://github.com/stevemolitor/claude-code.el][claude-code.el]]

• I switch between different CLI-based AI tools in Emacs: Claude Code / OpenAI Codex / Gemini CLI / etc. If you also use different AI tools inside Emacs, but want to keep the same user interface and experience, this package is for you.

• If you are choosing between the main AI coding packages in Emacs, ask one question first: do you want the deepest integration for one specific agent runtime, or do you want one Emacs workflow that stays stable even when you change AI tools?

• ai-code-interface.el is built for the second case. Its real advantage is not just backend coverage. Its main advantage is workflow portability: the same menu, context gathering, prompt flow, refactoring commands, TDD helpers, review workflow, prompt files, and Emacs MCP tools continue to work while the backend changes underneath.

| Package | Built around | Choose it when | |----------------------+---------------------------------+----------------| | ai-code-interface.el | One workflow across backends | You switch AI tools but want one stable Emacs workflow | | claude-code-ide.el | Claude Code inside Emacs | Claude Code is your main runtime | | agent-shell | ACP shell sessions | You prefer shell-first agent workflows and transcripts | | eca-emacs | An ECA-centered chat workspace | You want a polished server-backed chat UX |

• All four packages aim to keep AI-assisted development inside Emacs. The difference is what stays fixed. In =claude-code-ide.el=, the center is Claude Code. In =agent-shell=, the center is the ACP shell session. In =eca-emacs=, the center is the ECA workspace. In =ai-code-interface.el=, the center is your development workflow inside Emacs.

• That distinction matters if you do not want to commit to a single winner forever. You can use Claude Code for one task, Codex for another, Gemini CLI for a third, and still keep the same habits inside Emacs: the same entry points, the same context model, and the same review-oriented development flow. You are changing the backend, not changing how you work.

• Screenshot

[[./transient_menu.png]]

** New User Quick Start

If you are new to this package, follow this order:

1. Read this section
2. Run the setup in Installation

... View full README on GitHub