Linux command
rekal 命令
文本
复制后可按需替换文件名、目录或参数。
常用示例
Initialize
rekal init
Capture
rekal checkpoint
Search
rekal "[search query]"
Search
rekal --file [src/billing/] "[discount logic]"
View
rekal log
Drill into
rekal query --session [session_id] --full
Push
rekal push
Sync
rekal sync
说明
rekal captures AI session context at every git commit, creating a permanent, append-only record of development reasoning and conversations alongside code changes. It stores two databases: a shared data.db (turns, tool calls, checkpoints, files touched — distributed via a dedicated git orphan branch) and a local index.db (full-text index, vector embeddings, file co-occurrence graphs) used only for search. The tool installs git hooks so checkpoints are written automatically on every commit. Retrieval is a hybrid of BM25 lexical search, LSA, and Nomic vector embeddings, returning scored JSON with the best-matching turn index for progressive drill-down. A session of 2–10 MB of raw transcripts compresses to roughly 300 bytes on disk. Embeddings ship with the binary — no API keys, accounts, or external services.
参数
- init
- Initialize rekal in the current git repository
- clean
- Remove rekal setup from the repository
- checkpoint
- Capture current AI session context at the latest commit
- push _--force_
- Push rekal data to the remote branch
- sync _--self_
- Sync team context from remote branches
- index
- Rebuild the local search index database
- log _--limit n_
- Show recent checkpoints
- query --session _id_ _--full_ _--offset n_ _--limit n_
- Drill into a specific session with optional pagination
- query _"SQL"_ _--index_
- Execute a raw SQL query against the data or index database
- version
- Print CLI version
- --file _path_
- Scope search to a specific file or directory
- --role _human_
- Filter search results to human turns only
FAQ
What is the rekal command used for?
rekal captures AI session context at every git commit, creating a permanent, append-only record of development reasoning and conversations alongside code changes. It stores two databases: a shared data.db (turns, tool calls, checkpoints, files touched — distributed via a dedicated git orphan branch) and a local index.db (full-text index, vector embeddings, file co-occurrence graphs) used only for search. The tool installs git hooks so checkpoints are written automatically on every commit. Retrieval is a hybrid of BM25 lexical search, LSA, and Nomic vector embeddings, returning scored JSON with the best-matching turn index for progressive drill-down. A session of 2–10 MB of raw transcripts compresses to roughly 300 bytes on disk. Embeddings ship with the binary — no API keys, accounts, or external services.
How do I run a basic rekal example?
Run `rekal init` in a terminal, then adjust file names, paths, flags, or remote targets for your system.
What does init do in rekal?
Initialize rekal in the current git repository