mirror of
https://gitee.com/wanwujie/deer-flow
synced 2026-04-22 13:44:46 +08:00
* refactor: extract shared utils to break harness→app cross-layer imports Move _validate_skill_frontmatter to src/skills/validation.py and CONVERTIBLE_EXTENSIONS + convert_file_to_markdown to src/utils/file_conversion.py. This eliminates the two reverse dependencies from client.py (harness layer) into gateway/routers/ (app layer), preparing for the harness/app package split. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * refactor: split backend/src into harness (deerflow.*) and app (app.*) Physically split the monolithic backend/src/ package into two layers: - **Harness** (`packages/harness/deerflow/`): publishable agent framework package with import prefix `deerflow.*`. Contains agents, sandbox, tools, models, MCP, skills, config, and all core infrastructure. - **App** (`app/`): unpublished application code with import prefix `app.*`. Contains gateway (FastAPI REST API) and channels (IM integrations). Key changes: - Move 13 harness modules to packages/harness/deerflow/ via git mv - Move gateway + channels to app/ via git mv - Rename all imports: src.* → deerflow.* (harness) / app.* (app layer) - Set up uv workspace with deerflow-harness as workspace member - Update langgraph.json, config.example.yaml, all scripts, Docker files - Add build-system (hatchling) to harness pyproject.toml - Add PYTHONPATH=. to gateway startup commands for app.* resolution - Update ruff.toml with known-first-party for import sorting - Update all documentation to reflect new directory structure Boundary rule enforced: harness code never imports from app. All 429 tests pass. Lint clean. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: add harness→app boundary check test and update docs Add test_harness_boundary.py that scans all Python files in packages/harness/deerflow/ and fails if any `from app.*` or `import app.*` statement is found. This enforces the architectural rule that the harness layer never depends on the app layer. Update CLAUDE.md to document the harness/app split architecture, import conventions, and the boundary enforcement test. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: add config versioning with auto-upgrade on startup When config.example.yaml schema changes, developers' local config.yaml files can silently become outdated. This adds a config_version field and auto-upgrade mechanism so breaking changes (like src.* → deerflow.* renames) are applied automatically before services start. - Add config_version: 1 to config.example.yaml - Add startup version check warning in AppConfig.from_file() - Add scripts/config-upgrade.sh with migration registry for value replacements - Add `make config-upgrade` target - Auto-run config-upgrade in serve.sh and start-daemon.sh before starting services - Add config error hints in service failure messages Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix comments * fix: update src.* import in test_sandbox_tools_security to deerflow.* Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: handle empty config and search parent dirs for config.example.yaml Address Copilot review comments on PR #1131: - Guard against yaml.safe_load() returning None for empty config files - Search parent directories for config.example.yaml instead of only looking next to config.yaml, fixing detection in common setups Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: correct skills root path depth and config_version type coercion - loader.py: fix get_skills_root_path() to use 5 parent levels (was 3) after harness split, file lives at packages/harness/deerflow/skills/ so parent×3 resolved to backend/packages/harness/ instead of backend/ - app_config.py: coerce config_version to int() before comparison in _check_config_version() to prevent TypeError when YAML stores value as string (e.g. config_version: "1") - tests: add regression tests for both fixes Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix: update test imports from src.* to deerflow.*/app.* after harness refactor Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
47 lines
1.6 KiB
Python
47 lines
1.6 KiB
Python
"""Bash command execution subagent configuration."""
|
|
|
|
from deerflow.subagents.config import SubagentConfig
|
|
|
|
BASH_AGENT_CONFIG = SubagentConfig(
|
|
name="bash",
|
|
description="""Command execution specialist for running bash commands in a separate context.
|
|
|
|
Use this subagent when:
|
|
- You need to run a series of related bash commands
|
|
- Terminal operations like git, npm, docker, etc.
|
|
- Command output is verbose and would clutter main context
|
|
- Build, test, or deployment operations
|
|
|
|
Do NOT use for simple single commands - use bash tool directly instead.""",
|
|
system_prompt="""You are a bash command execution specialist. Execute the requested commands carefully and report results clearly.
|
|
|
|
<guidelines>
|
|
- Execute commands one at a time when they depend on each other
|
|
- Use parallel execution when commands are independent
|
|
- Report both stdout and stderr when relevant
|
|
- Handle errors gracefully and explain what went wrong
|
|
- Use absolute paths for file operations
|
|
- Be cautious with destructive operations (rm, overwrite, etc.)
|
|
</guidelines>
|
|
|
|
<output_format>
|
|
For each command or group of commands:
|
|
1. What was executed
|
|
2. The result (success/failure)
|
|
3. Relevant output (summarized if verbose)
|
|
4. Any errors or warnings
|
|
</output_format>
|
|
|
|
<working_directory>
|
|
You have access to the sandbox environment:
|
|
- User uploads: `/mnt/user-data/uploads`
|
|
- User workspace: `/mnt/user-data/workspace`
|
|
- Output files: `/mnt/user-data/outputs`
|
|
</working_directory>
|
|
""",
|
|
tools=["bash", "ls", "read_file", "write_file", "str_replace"], # Sandbox tools only
|
|
disallowed_tools=["task", "ask_clarification", "present_files"],
|
|
model="inherit",
|
|
max_turns=30,
|
|
)
|