Migration from Docker to Standalone Python Server (#73)
* Migration from docker to standalone server Migration handling Fixed tests Use simpler in-memory storage Support for concurrent logging to disk Simplified direct connections to localhost * Migration from docker / redis to standalone script Updated tests Updated run script Fixed requirements Use dotenv Ask if user would like to install MCP in Claude Desktop once Updated docs * More cleanup and references to docker removed * Cleanup * Comments * Fixed tests * Fix GitHub Actions workflow for standalone Python architecture - Install requirements-dev.txt for pytest and testing dependencies - Remove Docker setup from simulation tests (now standalone) - Simplify linting job to use requirements-dev.txt - Update simulation tests to run directly without Docker Fixes unit test failures in CI due to missing pytest dependency. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Remove simulation tests from GitHub Actions - Removed simulation-tests job that makes real API calls - Keep only unit tests (mocked, no API costs) and linting - Simulation tests should be run manually with real API keys - Reduces CI costs and complexity GitHub Actions now only runs: - Unit tests (569 tests, all mocked) - Code quality checks (ruff, black) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Fixed tests * Fixed tests --------- Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
committed by
GitHub
parent
9d72545ecd
commit
4151c3c3a5
@@ -17,15 +17,17 @@ from .base import BaseTool, ToolRequest
|
||||
# Field descriptions to avoid duplication between Pydantic and JSON schema
|
||||
THINKDEEP_FIELD_DESCRIPTIONS = {
|
||||
"prompt": (
|
||||
"Your current thinking/analysis to extend and validate. IMPORTANT: Before using this tool, Claude MUST "
|
||||
"first think hard and establish a deep understanding of the topic and question by thinking through all "
|
||||
"relevant details, context, constraints, and implications. Share these extended thoughts and ideas in "
|
||||
"the prompt so the model has comprehensive information to work with for the best analysis."
|
||||
"MANDATORY: you MUST first think hard and establish a deep understanding of the topic and question by thinking through all "
|
||||
"relevant details, context, constraints, and implications. Provide your thought-partner all of your current thinking/analysis "
|
||||
"to extend and validate. Share these extended thoughts and ideas in "
|
||||
"the prompt so your assistant has comprehensive information to work with for the best analysis."
|
||||
),
|
||||
"problem_context": "Additional context about the problem or goal. Be as expressive as possible.",
|
||||
"problem_context": "Provate additional context about the problem or goal. Be as expressive as possible. More information will "
|
||||
"be very helpful to your thought-partner.",
|
||||
"focus_areas": "Specific aspects to focus on (architecture, performance, security, etc.)",
|
||||
"files": "Optional file paths or directories for additional context (must be FULL absolute paths to real files / folders - DO NOT SHORTEN)",
|
||||
"images": "Optional images for visual analysis - diagrams, charts, system architectures, or any visual information to analyze",
|
||||
"files": "Optional absolute file paths or directories for additional context (must be FULL absolute paths to real files / folders - DO NOT SHORTEN)",
|
||||
"images": "Optional images for visual analysis - diagrams, charts, system architectures, or any visual information to analyze. "
|
||||
"(must be FULL absolute paths to real files / folders - DO NOT SHORTEN)",
|
||||
}
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user