greatmengqi
27b66d6753
Introduce an always-on auth layer with auto-created admin on first boot, multi-tenant isolation for threads/stores, and a full setup/login flow. Backend - JWT access tokens with `ver` field for stale-token rejection; bump on password/email change - Password hashing, HttpOnly+Secure cookies (Secure derived from request scheme at runtime) - CSRF middleware covering both REST and LangGraph routes - IP-based login rate limiting (5 attempts / 5-min lockout) with bounded dict growth and X-Forwarded-For bypass fix - Multi-worker-safe admin auto-creation (single DB write, WAL once) - needs_setup + token_version on User model; SQLite schema migration - Thread/store isolation by owner; orphan thread migration on first admin registration - thread_id validated as UUID to prevent log injection - CLI tool to reset admin password - Decorator-based authz module extracted from auth core Frontend - Login and setup pages with SSR guard for needs_setup flow - Account settings page (change password / email) - AuthProvider + route guards; skips redirect when no users registered - i18n (en-US / zh-CN) for auth surfaces - Typed auth API client; parseAuthError unwraps FastAPI detail envelope Infra & tooling - Unified `serve.sh` with gateway mode + auto dep install - Public PyPI uv.toml pin for CI compatibility - Regenerated uv.lock with public index Tests - HTTP vs HTTPS cookie security tests - Auth middleware, rate limiter, CSRF, setup flow coverage
48 lines
1.8 KiB
Python
48 lines
1.8 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`
|
|
- Deployment-configured custom mounts may also be available at other absolute container paths; use them directly when the task references those mounted directories
|
|
</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=60,
|
|
)
|