Add LSP interface parity, feature-ideas roadmap, and Semahub vision#100
Merged
Conversation
Added LSP as a dedicated interface column in the tool parity matrix. LSP is a specialized Language Server Protocol for IDE integration (hover, go-to-definition, find-references, symbol search). Only search and code-search have LSP support— LSP provides read-only navigation features, not high-level analysis. Updated legend and added LSP Interface Details section explaining: - 5 JSON-RPC methods: textDocument/hover, definition, references, documentSymbol, workspace/symbol - Mapping to gitsema operations (semantic search, symbol lookup) - Why most tools are not applicable to IDE protocol All maintenance, analysis, workflow, and visualization tools correctly marked as not available in LSP since it's for IDE navigation only. https://claude.ai/code/session_01EQQxujvhrBMVsHbYdoujKE
Created new canonical reference document for feature ideas not yet in active development (PLAN.md) or fully designed. Staging area for medium-term product direction and "what now?" questions. Documented intended features: - LSP --remote flag for querying remote HTTP-based index - LSP WebSocket transport for IDE connectivity through firewalls - LSP structural navigation using knowledge graph edges (Phase 107+) - LSP diagnostics and code lens (hotspots, debt, churn metrics) - MCP --remote delegation (parallel to LSP) - MCP HTTP transport (MCP over JSON-RPC/HTTP) - Improved LSP hover with temporal and risk data Each feature includes: - Problem statement - Intended behavior (code examples) - Design gaps (checklist of decisions needed) - Data dependencies (which phases required) - Effort estimates - Prerequisites Included deployment modes matrix showing progression from local to remote to HTTP-based access patterns. Updated CLAUDE.md to add feature-ideas.md to canonical documentation (5 core reference docs now). https://claude.ai/code/session_01EQQxujvhrBMVsHbYdoujKE
Documented vision for Semahub: a hosted semantic indexing platform where users register repos and gitsema handles indexing as a service. Architecture: - Separate Semahub project (user auth, billing, job queue, storage) - Load-balanced gitsema servers with multi-tenant support - S3/MinIO for index storage, PostgreSQL for metadata - Token-based authentication Gitsema changes needed (~1200 LOC): - gitsema auth login/logout/token commands - Service configuration (service.url, service.token) - HTTP multi-tenancy support (user isolation, quotas) - Remote indexing delegation (index start --service semahub) - Index sync (push/pull/sync) Semahub project (separate, ~5000-7000 LOC): - User signup/login, OAuth2 support - Repository registry and access control - Indexing job queue orchestration - Index storage and lifecycle management - Billing and subscription tiers - Web dashboard - API authentication and rate limiting MVP approach: Start with auth + service config in gitsema, then build Semahub gradually (user signup → storage → job queue → dashboard). Includes deployment modes matrix showing progression across all features, design gaps checklist, and competitive positioning. Effort: 2-3 weeks (gitsema) + 6-8 weeks (Semahub) for MVP. https://claude.ai/code/session_01EQQxujvhrBMVsHbYdoujKE
…s layer on top Restructured feature-ideas.md to clarify the strategic vision: **Layer 1: Self-Hosted Remote MCP (Phase 112-113)** - Extends gitsema with LSP --remote, MCP --remote, MCP HTTP/WebSocket - Enables distributed teams: developers on A, index on B - All infrastructure already exists from Phase 101+ (HTTP API, multi-tenancy) - New work: remote delegation flags + WebSocket transport **Layer 2: Semahub SaaS (Built on Layer 1)** - Not a separate architecture—wraps Layer 1 with user management - Adds: signup/login, billing, managed S3 storage, job queue - Users use same gitsema auth/tools commands, Semahub provides endpoint - Revenue model: per-user subscription + compute costs Key insight: Semahub is NOT the priority. Self-hosted remote MCP is the foundation that both self-hosted teams AND Semahub depend on. Updated all sections: - MCP Remote Delegation: clarified as foundation (Phase 112-113) - Architecture: two-layer diagram (foundation + managed) - What gitsema Needs: clarified ~1500-2000 LOC for Phases 112-113 - What Semahub Needs: clarified it's thin layer on top (user mgmt + billing) - Deployment Modes: separate tables for Layer 1 (self-hosted) vs Layer 2 (SaaS) - Strategy: two tiers with clear timeline This positions gitsema as open-source semantic engine with optional managed tier, similar to Tailscale (open-source core, managed SaaS option). https://claude.ai/code/session_01EQQxujvhrBMVsHbYdoujKE
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Comprehensive documentation for gitsema's interface parity, undesigned feature ideas, and long-term SaaS vision.
Changes
docs/parity.md(canonical reference)docs/feature-ideas.md(new canonical reference)--remoteflag) for querying remote indexUpdated
CLAUDE.mdStrategic Clarity
Two-layer architecture:
Layer 1: Self-Hosted Remote MCP (Phase 112-113) — Foundation
Layer 2: Semahub SaaS (Post-Phase 113) — Built on foundation
Why This Matters
Files Changed
docs/parity.md(new, 437 lines)docs/feature-ideas.md(new, 700+ lines, includes all ideas above)CLAUDE.md(updated references).changeset/tool-parity-tables.md(changeset)Note: LSP currently only supports semantic search and symbol navigation. This PR documents the intended expansion to structural analysis, risk scoring, and remote delegation—all designed to build on existing infrastructure (Phase 101-110).
Generated by Claude Code