ai-code-interface.el
Consolidates multiple AI coding assistants into one Emacs workflow, eliminating context switching and tool fragmentation while reducing vendor lock-in risk a…
Unified Emacs interface supporting OpenAI Codex, GitHub Copilot CLI, Claude Code, Gemini CLI, Opencode, and more
- Ask Claude to generate code snippets directly within your Emacs editor
- Refactor existing functions by sending them to Claude and receiving improved versions
- Autocomplete complex code blocks using multiple AI providers from one interface
Consolidates multiple AI coding assistants into one Emacs workflow, eliminating context switching and tool fragmentation while reducing vendor lock-in risk across development teams.
Emacs-based development teams evaluating or comparing multiple LLM-powered code assistants without rewriting tooling.
https://github.com/tninja/ai-code-interface.el
By tninja
How to Get It
claude plugins install tninja/ai-code-interface.el
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Generate code snippets directly within my Emacs editor
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Reddit
- (Release) Emacs front-end integrating multiple AI coding CLI tools, ai-code-inte — Reddit · 34 pts
- Best Claude Code Emacs integration — Reddit · 26 pts
- openspec.el - Interface for OpenSpec, a tool for spec-driven AI coding assistant — Reddit · 20 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 271 GitHub stars; 22 contributors; last commit 1d ago; license Apache-2.0.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 271 GitHub stars; 22 contributors; last commit 1d ago; license Apache-2.0.