docs: plan private CompText Context MCP#17
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces the implementation plan, design specification, and design review documents for a Windows-first private local Model Context Protocol (MCP) server for CompText. The feedback points out two key improvements for the implementation plan: first, the setuptools package discovery configuration in pyproject.toml must be updated to find packages under the new src/ directory to prevent installation and import errors; second, the planned compatibility helper for Path.is_relative_to is unnecessary because the method is natively supported in Python 3.9 and above, including the target Python 3.10+ runtime.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - [ ] **Step 1: Add the minimum runtime dependencies** | ||
|
|
||
| Add optional dependency group and entry point without enabling network behavior: | ||
|
|
||
| ```toml | ||
| [project.optional-dependencies] | ||
| mcp = [ | ||
| "mcp>=1.9,<2", | ||
| "pydantic>=2.7,<3", | ||
| "tomli-w>=1.0,<2; python_version < '3.11'", | ||
| ] | ||
|
|
||
| [project.scripts] | ||
| comptext = "comptext.cli:main" | ||
| comptext-mcp = "comptext.cli.mcp:main" | ||
| ``` | ||
|
|
||
| Preserve existing dependencies and scripts; merge rather than replace existing tables. |
There was a problem hiding this comment.
The plan specifies moving the codebase to a src/comptext/ structure and using comptext.cli:main as the entry point. However, the existing pyproject.toml is configured with:\n\ntoml\n[tool.setuptools.packages.find]\ninclude = [\"modules*\"]\n\n\nIf this is not updated to discover packages in the src/ directory, the new comptext package will not be found or installed during python -m build or pip install, leading to ModuleNotFoundError when running tests or the CLI.\n\nPlease update Step 1 to explicitly include updating the setuptools package discovery configuration in pyproject.toml to find packages under src/ (e.g., by adding where = [\"src\"] and updating include).
| return candidate | ||
| ``` | ||
|
|
||
| On Python 3.10, provide an internal compatibility helper instead of calling `Path.is_relative_to` directly. Resolve configured roots during startup, reject duplicate names, and never accept a root from a tool request. |
There was a problem hiding this comment.
The plan mentions providing an internal compatibility helper instead of calling Path.is_relative_to directly on Python 3.10. However, Path.is_relative_to was introduced in Python 3.9, so it is fully supported natively in Python 3.10+. You can safely call Path.is_relative_to directly without any compatibility helpers, simplifying the implementation.
1 participant
Ziel
Vollständige Designspezifikation und ausführbarer TDD-Implementierungsplan für einen privaten Windows-first CompText Context MCP.
Enthalten
stdiofür Codex Desktopcomptext-codexDateien
docs/superpowers/specs/2026-07-13-private-context-mcp-design.mddocs/superpowers/specs/2026-07-13-private-context-mcp-design.review.mddocs/superpowers/plans/2026-07-13-private-context-mcp.mdStatus
Nur Planung und Review; keine Runtime- oder Produktionsänderung. Der Implementierungsplan umfasst zehn unabhängig prüfbare TDD-Aufgaben.