docs: add Entroly context optimization integration#6052
Conversation
📝 WalkthroughWalkthroughThis PR adds documentation for the Entroly Context Optimization integration with CrewAI. It introduces a new detailed documentation page explaining Entroly's context compression capabilities and provides setup instructions for both proxy and library modes, plus references the local dashboard and feature summary. ChangesEntroly Integration Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Warning |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
docs/en/tools/integration/overview.mdx (1)
25-27: ⚡ Quick winConsider qualifying the "70-95%" cost reduction claim.
The percentage range is specific and prominent, but the overview card doesn't indicate which scenarios achieve the higher vs lower end of the range. Readers might expect 70-95% savings across all use cases. Other integration cards in this overview focus more on capabilities ("access hundreds of tools", "invoke live automations") rather than quantified outcome claims.
While the PR objectives note this claim is backed by benchmarks, consider whether the overview card should either:
- Add brief context: "Reduce LLM API costs by up to 70-95% depending on workload..."
- Or soften to: "Significantly reduce LLM API costs with local context compression..."
- Or defer the percentage to the detailed page where benchmark context can be explained
This helps set realistic expectations before users click through to the full documentation.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/en/tools/integration/overview.mdx` around lines 25 - 27, The overview Card with title "Entroly Context Optimization" makes a specific "Reduce LLM API costs by 70-95%" claim without context; update the Card copy to either add qualifying context ("Reduce LLM API costs by up to 70-95% depending on workload and cache hit rates") or soften it to a non-quantified statement ("Significantly reduce LLM API costs with local context compression"), or remove the percentage here and move the benchmark details to the linked page (/en/tools/integration/entrolytool) so the overview remains consistent with other cards; edit the Card element text accordingly to reflect the chosen approach.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@docs/en/tools/integration/overview.mdx`:
- Around line 25-27: The overview Card with title "Entroly Context Optimization"
makes a specific "Reduce LLM API costs by 70-95%" claim without context; update
the Card copy to either add qualifying context ("Reduce LLM API costs by up to
70-95% depending on workload and cache hit rates") or soften it to a
non-quantified statement ("Significantly reduce LLM API costs with local context
compression"), or remove the percentage here and move the benchmark details to
the linked page (/en/tools/integration/entrolytool) so the overview remains
consistent with other cards; edit the Card element text accordingly to reflect
the chosen approach.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 01d46df4-ae68-427a-8aa1-a9e6c7d62a28
📒 Files selected for processing (2)
docs/en/tools/integration/entrolytool.mdxdocs/en/tools/integration/overview.mdx
What this PR adds
Adds Entroly as an integration tool in the CrewAI docs.
Files changed:
docs/en/tools/integration/entrolytool.mdx— Full integration guidedocs/en/tools/integration/overview.mdx— Added card to the integration overviewWhy this fits CrewAI:
Multi-agent CrewAI workflows multiply token costs because each agent independently sends large context windows. Entroly addresses this specifically:
Integration is transparent:
\\�ash
pip install entroly && entroly proxy
\\
\\python
os.environ['OPENAI_BASE_URL'] = 'http://localhost:9377/v1'
CrewAI works as normal — Entroly compresses context transparently
\\
Apache-2.0, local-first, no outbound analytics by default. All benchmark claims backed by committed JSON artifacts.
Summary by CodeRabbit