mirror of
https://github.com/langbot-app/LangBot.git
synced 2026-06-27 16:04:21 +00:00
Junyan Chin
e9dd584792
* feat(api): support global API key from config.yaml (api.global_api_key) Accept a config-defined global API key anywhere a web-UI key is accepted (X-API-Key / Bearer), with no login session and no DB record. Useful for automated deployments and AI agents (HTTP API + MCP). Defaults to empty (disabled); does not require the lbk_ prefix. - templates/config.yaml: add api.global_api_key with security notes - service/apikey.py: verify_api_key checks global key first (constant-time) - docs/API_KEY_AUTH.md: document the global key + security guidance - tests: cover global-key match, prefix-free, fallback-to-db, disabled * feat(mcp): expose LangBot management as an MCP server at /mcp Add an MCP (Model Context Protocol) server so external AI agents can manage a LangBot instance. Reuses the same API-key auth as the HTTP API (including the config.yaml global API key). - pkg/api/mcp/server.py: FastMCP server wrapping the service layer; 21 curated tools across system/bots/pipelines/models/knowledge/mcp-servers/skills - pkg/api/mcp/mount.py: ASGI dispatcher fronting Quart; authenticates /mcp requests with an API key, runs the streamable-HTTP session manager lifespan - controller/main.py: serve the wrapped ASGI app via hypercorn (was run_task) - web: new 'MCP' tab in the API integration dialog showing endpoint, auth, and client config; i18n for 8 locales - tests/manual/mcp_smoke.py: e2e check (401 unauth, list tools, call tools) Tool surface is intentionally curated (not all ~25 route groups) to keep the agent surface small, safe, and maintainable. Extend deliberately. * feat(skills): add in-repo skills/ as the single source of truth Migrate the agent skills + QA/e2e test harness from the (now archived) langbot-app/langbot-skills repo into LangBot/skills/, and add four new skills. Migrated: - langbot-plugin-dev, langbot-testing (e2e), langbot-env-setup, langbot-skills-maintenance, langbot-eba-adapter-dev - the bin/lbs CLI (src/, test/, scripts/, schemas/, qa-agent-docs/) New: - langbot-dev core backend + web development - langbot-deploy Docker/K8s deployment + config.yaml + global API key - langbot-mcp-ops operating the LangBot MCP server (/mcp) - langbot-space-ops operating the Space marketplace MCP server - src/cli.ts repoRoot(): recognize the skills assets root (skills.index.json + bin/lbs) so the CLI works when nested inside the LangBot repo - README.md: unified skill catalog; skills.index.json regenerated Parity with source verified: bin/lbs validate + node test suite match the source repo (only the uncommitted .lbpkg build-artifact fixture differs). * docs(agents): document agent-facing surfaces + API/MCP/skills sync rule * docs(readme): add 'Built for AI Agents' section across all locales Highlight MCP server, in-repo skills (single source of truth), AGENTS.md sync rule, and llms.txt. Cross-link LangBot Space MCP marketplace. * style(mcp): fix ruff format + prettier lint in MCP server and API panel * style(web): prettier format MCP i18n locale entries * docs(skills): note MCP instance control in dev/testing skills All development-guidance skills now point to the LangBot instance MCP server (/mcp) and the Space marketplace MCP server, reusing API keys.
52 lines
2.1 KiB
YAML
52 lines
2.1 KiB
YAML
id: dify-agent-debug-chat
|
|
title: "Dify AgentRunner returns a response through Pipeline Debug Chat"
|
|
mode: agent-browser
|
|
area: pipeline
|
|
type: provider
|
|
priority: p2
|
|
risk: medium
|
|
ci_eligible: false
|
|
tags:
|
|
- dify
|
|
- agent-runner
|
|
- pipeline
|
|
skills:
|
|
- langbot-env-setup
|
|
- langbot-testing
|
|
env:
|
|
- LANGBOT_FRONTEND_URL
|
|
- LANGBOT_BACKEND_URL
|
|
preconditions:
|
|
- "A Dify app Service API key is available from the active secret source and must not be printed in reports."
|
|
- "The target pipeline is safe to modify for Dify runner configuration."
|
|
steps:
|
|
- "Ensure a Dify app Service API key is available from the active secret source."
|
|
- "Open LANGBOT_FRONTEND_URL."
|
|
- "Navigate to Pipelines and open the target pipeline."
|
|
- "Open Configuration > AI."
|
|
- "Select runner Dify."
|
|
- "Set Base URL, App Type, API Key, Base Prompt, and Timeout according to references/dify-agent-runner.md."
|
|
- "Save the pipeline."
|
|
- "Open Debug Chat."
|
|
- "Send a prompt asking the bot to reply exactly with a unique sentinel, for example LANGBOT_DIFY_OK_<date>."
|
|
checks:
|
|
- "UI: The runner selector and runner config identify Dify, not a generic Default label."
|
|
- "UI: Debug Chat shows a Bot message containing the sentinel."
|
|
- "History/log validation: The sentinel is present in an assistant/bot message, not only in the echoed User message."
|
|
- "Logs: Backend logs show Dify /chat-messages returned HTTP 200 and Conversation(0) Streaming completed."
|
|
- "Console: No unexpected frontend errors appear during runner configuration or Debug Chat."
|
|
- "Secret safety: No Dify API key, JWT, or browser token is printed in reports."
|
|
evidence_required:
|
|
- ui
|
|
- console
|
|
- backend_log
|
|
diagnostics:
|
|
- "Use direct Dify streaming API only to distinguish invalid Dify credentials from LangBot runner failures."
|
|
- "If direct Dify blocking mode fails for an Agent Chat app, retry streaming before treating credentials as invalid."
|
|
- "Use GET /api/v1/pipelines/{uuid} only to confirm saved runner_config."
|
|
troubleshooting:
|
|
- agent-runner-actor-context-fields
|
|
- ambiguous-runner-default-label
|
|
- plugin-runtime-timeout
|
|
- proxy-env-mismatch
|