AICHE +

W

Warp Integration

The short answer: open Warp, click into the command input or a text editor, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak your commit message, documentation, or description, and AICHE inserts the text directly into Warp.

Warp already has AI built in. Warp AI suggests commands, explains error output, and helps construct complex pipelines. So why would you add AICHE?

Because they do different things. Warp AI helps you write commands - the technical syntax that talks to the machine. AICHE helps you write text - the human-readable prose that talks to people. Commit messages, script documentation, README content, Warp Drive workflow descriptions, and inline code comments. Warp AI does not write your commit messages for you. It does not draft your README. It does not explain why your deployment script works the way it does. That is where voice comes in.

Warp's block-based output model is actually a good fit for interleaving voice-dictated text with command output. Each block is a discrete unit. Your dictated documentation can sit in context alongside the commands and output it describes.

1. Open Warp terminal.
2. Navigate to your project directory.
3. For commit messages: type git commit to open your editor, then press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux).
4. Speak your content naturally - commit messages, documentation, descriptions.
5. Press the hotkey again. AICHE inserts the text at your cursor.
6. For prompt-level text, review and press Enter. For editor text, save and close.
7. Use Warp AI separately for command syntax when needed.

Heads-up: AICHE and Warp AI do not interfere with each other. AICHE is a separate desktop app that inserts text via the operating system. Warp AI operates within Warp's command input. You can use both in the same session without conflicts.

Commit Messages in Warp

Using Warp's Editor for Detailed Commits

Warp's input area is a full text editor, not a simple command prompt. You can write multi-line text, use arrow keys to navigate, and edit before pressing Enter. This makes it a good environment for composing commit messages.

Type git commit, let your configured editor open, and press ⌃+⌥+R. Speak the full message: subject line with a clear summary, then the body with context about why the change was made, what alternatives you considered, and what the reviewer should pay attention to.

Warp's block output means the commit result (branch, hash, files changed) appears as a clean block below your command. Your git log builds up with meaningful messages, and Warp's searchable output history lets you find past commits quickly.

Quick Commit Messages

For smaller changes, type git commit -m " directly in Warp's input area. Press ⌃+⌥+R, speak the message, press the hotkey again, close the quote, and hit Enter. Warp's editor handles the inline text smoothly, and the resulting block shows the commit confirmation.

Warp Drive Workflow Descriptions

Documenting Shared Workflows

Warp Drive lets you save and share command workflows with your team. Each saved workflow has a description field explaining what it does, when to use it, and what parameters to adjust.

Open Warp Drive, create or edit a workflow, click into the description field, and dictate. Say "this workflow sets up a local development environment for the payments service. Runs database migrations, seeds test data, starts the service on port 3001, and tails the log file. Requires Docker running and the payments-db container started. Modify the PORT variable if 3001 is already in use. Expected startup time is about 15 seconds."

Documented workflows get adopted by the team. Undocumented workflows get ignored or misused. Voice makes the documentation step fast enough that it actually happens.

Command Annotations

When you save a complex command to Warp Drive, add a description explaining what each flag does and why. Your future self and your teammates should not have to decode kubectl get pods -n production -l app=api --field-selector=status.phase!=Running -o jsonpath='{.items[*].metadata.name}' from scratch. Dictate: "lists the names of all non-running pods in the production namespace for the api application. Used during deployments to identify pods that failed to start or are stuck in CrashLoopBackOff."

Documentation Creation in Terminal

README Files

When starting a new project, create the README immediately from Warp. Open your editor (vim README.md or nano README.md), press ⌃+⌥+R, and dictate the project overview, setup instructions, and usage examples. Speaking the README while the project structure is fresh in your mind produces better documentation than writing it later when you have forgotten the setup steps.

Script Headers and Comments

Shell scripts need documentation. Open a script in your preferred editor from Warp, navigate to the top, and dictate a header explaining the script's purpose, required arguments, dependencies, and expected behavior. For complex pipeline commands within the script, add inline comments by dictating what each section does.

Warp's syntax-highlighted command input makes it easy to see the structure of scripts. When you have a long pipeline visible in a Warp block, dictate an explanatory comment above it in your script file.

AICHE and Warp AI Together

Complementary Workflows

A practical workflow combining both tools: you need to write a deployment script. Use Warp AI to help construct individual commands (correct kubectl flags, proper docker compose syntax). Use AICHE to dictate the script's header documentation, inline comments explaining each step, and the README section describing how to use the script. One tool handles machine syntax; the other handles human explanation.

Error Investigation Notes

When a command fails and Warp AI explains the error, you might want to document the issue and resolution for your team. Open a markdown file, press ⌃+⌥+R, and dictate what went wrong, what Warp AI suggested, what actually fixed it, and what preventive measure you are adding. This documentation lives in your project and helps teammates who hit the same issue.

Warp-Specific Tips

• Block-based history. Warp organizes terminal output into blocks (each command and its output is one block). When you dictate text into a commit message or file, the resulting command output appears as a clean block you can search later.
• Warp Notebooks. If you use Warp's notebook feature for mixing commands and documentation, AICHE is ideal for the documentation sections. Dictate narrative text between command blocks to create runnable, documented procedures.
• Cross-platform. Warp runs on macOS, Windows, and Linux. AICHE runs on all three. The same voice workflow works regardless of which platform you are using Warp on.
• Command palette compatibility. Warp's command palette (Cmd+P or Ctrl+P) and AICHE's hotkey do not conflict. Both are keyboard-driven and operate independently.

The pro-tip: After a debugging session in Warp, scroll back through the command blocks and dictate a summary document. Describe what the issue was, what commands you ran to diagnose it, what you found, and how you fixed it. Warp's block history serves as an outline; your dictation adds the narrative.

Result: Commit messages with full context dictated in 15 seconds. Warp Drive workflows with descriptions that teammates can actually follow. Documentation created alongside commands instead of after the fact. Voice for the text, Warp AI for the syntax, and both working without conflict.

Do this now: Open Warp, navigate to a project with staged changes, type git commit, press ⌃+⌥+R, and dictate a commit message that covers what changed, why, and what to watch for.