AICHE +

C

Cody Integration

The short answer: open your IDE with Cody installed, open the Cody chat panel, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak your codebase question for 30-60 seconds, and AICHE inserts the formatted prompt for Cody to analyze.

Typing context-heavy prompts about enterprise codebases takes 8-12 minutes and breaks architectural thinking. You understand the system's authentication flow across 15 microservices, but explaining it to Cody requires typing service names, file paths, and interaction patterns.

1. Open your IDE (VS Code, JetBrains, Neovim) with Cody installed.
2. Open the Cody chat panel or sidebar.
3. Press your AICHE hotkey to start recording.
4. Speak your complete question with context (example: "Explain how the authentication flow works across our microservices architecture, specifically how JWT tokens are validated in the API gateway service, how they get passed to downstream services through request headers, and how token refresh works when access tokens expire after 15 minutes. Include the Redis caching layer we use for blacklisting revoked tokens and explain how we handle token revocation during logout across all active sessions").
5. Press the hotkey again-AICHE transcribes, applies Content Organization to structure multi-part questions, and inserts the text.
6. Press Enter and let Cody analyze your codebase to answer.

Heads-up: Cody searches your entire codebase for context, so mention specific service names, file types, or patterns you want it to focus on. Saying "in the auth-service" or "look at Redis integration" helps Cody narrow its search and provide more relevant answers.

The pro-tip: use voice to explain what you're trying to accomplish before asking how. Saying "I need to add rate limiting to prevent brute-force attacks on login, focusing on our existing Redis setup" gives Cody better context than just asking "how do I add rate limiting."

Result: architectural questions that took 10 minutes to type with full service context and technical detail now take 60 seconds to speak, and Cody provides better answers because your voice prompt included all the relevant system constraints.

Do this now: open Cody, press your hotkey, and ask one question about your codebase's architecture that you've been avoiding because typing the full context felt exhausting.