Usage
Arguments
The question or query to search for in Mubit memory.
Options
Working directory path. Defaults to current directory.
Mubit API key. Can also be set via
MUBIT_API_KEY environment variable.Mubit project ID. Auto-detected from git remote if not specified.
Mubit actor ID. Auto-detected from git config if not specified.
Run scope:
project or session.project: Search across all sessions in the projectsession: Search within specific session only
Output results in JSON format.
Maximum number of results to return.
Examples
Query recent changes
Query with project scope
Query with JSON output
Query specific project
Query Types
Mubit supports various query types:Code Changes
Decisions
Bug Fixes
Features
Refactoring
Output Format
Results include:- Matching events and sessions
- Relevance scores
- Timestamps
- Actor information
- Code snippets or summaries
JSON Output Example
Requirements
Mubit API Key
You must have a Mubit API key configured:Synced Data
Query results depend on data synced to Mubit:-
Run initial push:
-
Verify sync status:
Performance
- Queries typically return in under 2 seconds
- Results are ranked by semantic relevance
- Recent events are weighted higher
Privacy
Mubit query:- Only searches data you’ve explicitly pushed
- Respects project-level access controls
- Does not access other projects’ data
Related Commands
- codaph push - Push local history to Mubit
- codaph pull - Pull shared memory from Mubit
- codaph timeline - View local timeline
- codaph doctor - Diagnose Mubit connectivity