intentic plugin
intentic plugins for Claude Code: trimmed Bash output, a project map at session start and iq search used before grep
- 93 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Hooks modify Bash output before the model reads it and run the iq binary, which indexes the project and session transcripts.
Install
- Works in
Manual install
/plugin marketplace add intentic/intenticAdds the repository marketplace, then `/plugin install intentic@intentic`. The command is assembled from marketplace.json.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks modify Bash output before the model reads it and run the iq binary, which indexes the project and session transcripts.
This is third-party code. Review the repository files before installing.
What it does
The intentic repository ships a workspace for coding agents, and its Claude Code plugins live in the repository marketplace. The intentic plugin installs from npm as @intentic/claude-plugin. It trims Bash output before Claude reads it, shows a project map at session start and teaches the agent to use the iq code search and fileq document reading. The /intentic:stats command shows how much each mechanism saved. Every mechanism is a separate switch in /config. The second plugin, iq, installs a skill and a session-start nudge. It trains the agent to search the project with the iq command: a query picks its own strategy, whether a symbol, a path, a regular expression or a plain question. The answer opens with a block holding the top path:line anchor and a verdict of confident, ambiguous or weak, and the output fits the --budget token limit. The program itself needs the binary from the @intentic/iq npm package. The workspace itself runs Claude Code, Codex, Cursor and Gemini side by side, each in its own git worktree, inside a Docker sandbox on your machine. It needs a sign-in at app.intentic.dev, while the plugins work on their own.
Who it is for. Developers whose Claude Code sessions hit limits because of long command output and needless file reads in large repositories.
Good fit when
- Tests or builds print hundreds of lines and Claude spends context reading the whole log
- An agent in a monorepo searches for a function with grep and walks through dozens of files when a direct definition address is needed
- You want numbers on what each mechanism gave: /intentic:stats counts the savings separately
- The agent needs a direct answer to a question such as where access rights are checked, with file and line anchors
- An agent answer has to be verified in a hook or CI: `iq verify` checks file and line references against the index
Not a fit when
- The repository is small and plain grep works without an index
- You need several agents running in parallel branches: that is the job of the intentic workspace, not the plugins
- The agent needs full command output, for example to analyze a long log, and trimming it is unwanted
Example request
Use iq to find where the secrets floor is enforced and show file and line anchors.Limitations
The plugin works with Claude Code and the marketplace describes no other agents. iq needs a separate binary from npm, and the workspace README has no install command, so it is assembled from the description in marketplace.json. The index lives in .intentic/local/cache/iq inside the project and maintains itself, and `iq index rebuild` rebuilds it by hand. Trimming output changes what the model sees, so switching the mechanism off in /config helps when debugging. The cloud part of the workspace requires sign-in with Google or a mailed code. The savings figures in /intentic:stats come from the plugin itself.
How to disable. Disable the plugin through `/plugin` or turn off individual mechanisms in `/config`. Remove the iq binary with `npm uninstall -g @intentic/iq`, the index lives in `.intentic/local/cache/iq`.
FAQ
What ships in the intentic plugin?
Bash output trimming, a project map at session start, teaching the agent iq search and fileq document reading, and a /intentic:stats command with savings statistics. Each mechanism switches off in /config.
How does the iq plugin differ from intentic?
iq installs only a skill and a session-start nudge for code search and needs the `@intentic/iq` binary. The intentic package adds Bash output trimming and statistics on top.
How does iq answer a plain question?
The query picks its own approach: an address, a path, a name, a regular expression or semantic search when nothing matches exactly. The answer opens with a block holding the top anchor and a verdict of confident, ambiguous or weak.
Do the plugins need the intentic workspace?
No, they live in the repository marketplace and install through /plugin. The workspace with Docker and sign-in at app.intentic.dev is needed only to run agents in parallel branches.
How do I check an agent answer with iq?
`iq verify` reads an answer from a file or stdin and checks references: files must exist, path:line anchors must fall inside the file, code names must be defined. Exit code 1 reports a failure, so it fits a hook or CI step.
Discussion
No questions or reviews yet.
Related
PluginsA marketplace of eight Claude Code plugins: session memory, research, commits, skill authoring and more.
Ten Claude Code plugins: panes and bands above the prompt, secret handling, a vague-prompt filter and memory cleanup.
Plugins for git, Python and accessibility in one place: 400+ skills, subagents and hooks against dangerous agent commands.
Three Claude Code plugins: the savvy-flow orchestrator with tiered subagents and two mods for a progress panel and a cache timer
Claude Code Skills and Agents
Claude Code Skills & Agents
A Claude Code plugin bundling skills and sub-agents: deep research, image generation, GitHub work, code review and model switching
A Claude Code marketplace of four plugins: pasted image preview, a prompt cache meter, a prompt queue and a bridge to Codex.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| intentic (this card) | no | 93 | ||
| RTK | no | 86,384 | a CLI that compresses command output; intentic adds a project map, iq search and statistics | |
| Context Mode | no | not required | 34,013 | an MCP server that saves context; intentic is a Claude Code plugin with hooks and iq search |
README in short
The README describes the intentic workspace: parallel agents in separate branches, plan approval before code changes, a sandbox on your machine and running on your own subscriptions without markup. The plugins are described in marketplace.json and the iq package README.