Dexi VS git-sizer

• Unified capture
  Typed notes, saved web pages, highlights, forwarded email and RSS entries all become searchable notes in one workspace
• Semantic search
  Full-text plus embedding-based similarity search across notes, bookmarks, emails and feed entries; 'related notes' on every item
• Knowledge graph
  #hashtags, @mentions and [[wiki links]] build a 2D/3D graph automatically; structure emerges from writing, no folders required
• MCP server for AI agents
  OAuth 2.1-secured MCP endpoint (mcp.dexi.net) lets Claude, Claude Code, Hermes and OpenClaw search, read and write your notes, with per-connection access limits
• Web clipper
  Chrome extension, bookmarklet and iOS share sheet; save a page or a highlighted selection with a comment
• Save by email
  Personal save-<code>@my.dexi.net address; forward newsletters or emails and they land as notes
• RSS subscriptions
  Subscribe to feeds in-app; entries are ingested as notes and searchable alongside everything else
• Digests and published feeds
  Scheduled tag-filtered email digests, plus public RSS/JSON feeds curated from your notes
• Spaced repetition
  Tag notes into a review deck and drill them on an SM-2 schedule, with a daily reminder email
• Team sharing and export
  Per-note opt-in sharing with team-wide search (Team plan); ZIP, CSV and markdown export, no lock-in

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

No analysis of Dexi yet.

Tracking Dexi since Aug 2026.

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago