Claude Code
Companion CLI installs a UserPromptSubmit hook, collects safe repo context, and injects a droPrompt coding brief before Claude starts.
One prompt layer for Claude Code, Cursor, Codex, Gemini CLI, Antigravity, MCP clients, and any coding agent that can call an API. Turn rough requests into precise, project-aware task briefs with compact context and verification steps.
Each client gets the best available connection method: native hook where possible, MCP where supported, API where the tool can call HTTP, and copy-ready briefs when the tool has no integration surface yet.
Companion CLI installs a UserPromptSubmit hook, collects safe repo context, and injects a droPrompt coding brief before Claude starts.
Use droPrompt MCP/API for prompt enhancement and generate Cursor-ready rules or project instructions for IDE-assisted work.
Generate a professional task brief before launching Codex so the terminal agent gets scope, constraints, and test commands up front.
Call the coding brief endpoint or paste the enhanced task into Gemini CLI for cleaner coding sessions with less back-and-forth.
Use copy-ready briefs today; native setup depends on the available extension, MCP, or external-tool surface in the user’s Antigravity build.
For any tool that supports MCP or HTTP: send a request, get a compact task brief, then hand it to the coding agent.
The first direct installer is Claude Code. Other tools use MCP, API, or copy workflows until their native automation surface is confirmed.
Install once, paste your droPrompt API key from Dashboard → Account → API Keys, then let the hook enhance each coding request.
mkdir -p ~/.local/bin
curl -fsSL https://droprompt.com/install/droprompt-claude.mjs \
-o ~/.local/bin/droprompt-claude
chmod +x ~/.local/bin/droprompt-claude
droprompt-claude login
droprompt-claude setup
droprompt-claude statusWhether the request comes from a hook, MCP tool, API call, or manual paste, droPrompt converts it into a compact engineering brief before the agent burns tokens on discovery.
The developer types naturally, even if the task is vague or missing project details.
The integration adds safe signals: project type, scripts, branch, README, rules, and file hints.
The API turns intent plus context into a clean implementation task with boundaries.
Claude Code, Cursor, Codex, Gemini, or another agent starts with enough context to avoid blind exploration.
The brief includes tests, checks, and risk notes so the output is easier to trust.
Use API keys from the dashboard and send `X-API-Key` from CLIs, extensions, MCP servers, internal tools, or custom IDE automations.
POST /api/coding/briefPOST /api/coding/enhancePOST /api/claude-code/enhancePOST /api/generatePOST /api/refine / POST /api/enhanceGET /api/keys / POST /api/keysSend the rough task, target tool, and bounded project context. droPrompt returns `enhancedPrompt` and `injectedContext`.
curl -X POST https://droprompt.com/api/coding/brief \
-H "Content-Type: application/json" \
-H "X-API-Key: dp_..." \
-d '{
"client": "cursor",
"prompt": "fix checkout bug",
"context": {
"branch": "feature/payments",
"scripts": ["npm test"],
"hints": ["src/payment", "tests/payment"]
}
}'Claude Code direct hook is the first concrete installer. Cursor, Codex, Gemini CLI, Antigravity, and other tools are supported through the available surfaces listed here: MCP, API, generated rules, or copy-ready briefs. Native installers are added only when the tool exposes a reliable integration path.
API keys, coding brief API, Claude Code endpoint compatibility, manual/copy workflow, and MCP/API positioning.
Cursor rules/MCP documentation, Codex wrapper, Gemini CLI wrapper, and Antigravity workflow once native hooks are confirmed.
Bounded context by default: no `.env`, private keys, tokens, or full-source uploads unless a future team policy explicitly allows it.
Use droPrompt as the task-brief and context layer across Claude Code, Cursor, Codex, Gemini CLI, Antigravity, MCP tools, and your own developer automations.