gemqq

Gemini Quick Question is a one-shot wrapper for gemini-cli featuring interactive editor support, markdown rendering in terminal, and real-time token usage statistics. gemqq does not have memory nor context, it simply answers your 'quick questions' quickly.

Installation

npm install -g gemqq

Usage

gemqq [OPTIONS] [PROMPT...]

Options

• -e, --edit: Open prompt in default editor (EDITOR or VISUAL).
• -r, --raw: Output raw text (disable markdown rendering via glow).
• -j, --json: Output response as JSON.
• -c, --copy: Copy response to system clipboard.
• -m, --model NAME: Specify a custom model.
• --style NAME: Specify a glow style (e.g., auto, dark, light). Default is auto.
• --no-stats: Suppress token usage statistics and timing info.
• --project: Enable full project workspace context. By default, gemqq isolates file context to zero by running in a temporary directory. Use this flag when you want Gemini to see your codebase.
• --pro: Use gemini-3-pro-preview model.
• --flash: Use gemini-3-flash-preview model (Default).
• --debug: Enable debug mode.
• -h, --help: Show help message.

Token Statistics

By default, gemqq displays token usage and execution time: (Done in 5.9s, 4551 tokens (4502i / 2o))

• i: Input Tokens (Prompt)
• o: Output Tokens (Candidates)

Use --no-stats to hide this information.

Context Isolation

By default, gemqq executes the Gemini CLI in a temporary directory to isolate your file context to zero. This prevents Gemini from automatically snapshotting your current directory tree, which significantly reduces token usage and improves privacy for general queries.

If you need Gemini to analyze your codebase or reference local files, use the --project flag to run in your current working directory with full context enabled.

Examples

gemqq difference between gemini 3.0, 3.1. make a table
cat file.txt | gemqq summarize this
gemqq -e --pro
gemqq C++ operator precedence and keywords
gemqq how do I update git submodules in parent
gemqq --pro "Analyze the subtext of Roy's final speech in Blade Runner"

Note: Prompts do not require quotes unless they contain special shell characters like ?, *, &, ;, or |. If your prompt includes these, you should either quote it or escape the characters.

Testing

The project includes automated integration and unit tests using Vitest.

npm test

Contributing

I am currently not accepting external code contributions (Pull Requests) while I focus on the initial development. However, suggestions, bug reports, and feedback are very welcome!

Please feel free to:

• Open a Discussion for ideas and feedback.
• Open an Issue to report bugs.

Support

If you find this tool useful and would like to support its development, you can buy me a coffee.

Dependencies

• Gemini CLI
• Glow (for markdown rendering)