📄 工具详情 ⚙️ 安装教程 📚 使用教程
能力标签
🔌 MCP🤖 Agent🔄 工作流🐳 Docker💻 CLI🔗 REST API🔊 TTS🎙 STT🧠 Claude✨ GPT
⚙️
Agent工作流

开源AI工作流

基于 Go · 无代码搭建完整 AI 自动化流程
英文名：denkeeper
⭐ 9 Stars 🍴 1 Forks 💻 Go 📄 Apache-2.0 🏷 AI 7.5分
7.5AI 综合评分
workflowgo
⬇ 下载源码 ZIP ⚙️ 配置说明
✦ AI Skill Hub 推荐

开源AI工作流 是 AI Skill Hub 本期精选Agent工作流之一。综合评分 7.5 分，整体质量较高。我们推荐使用将其纳入你的 AI 工具库，帮助提升工作效率。

📚 深度解析
开源AI工作流 是一套完整的 AI Agent 自动化工作流方案。随着 AI 能力的不断提升，基于 Agent 的自动化工作流正在成为提升个人和团队效率的核心方式。区别于传统的 RPA 自动化（模拟鼠标键盘操作），AI Agent 工作流通过理解任务意图、动态规划执行路径，能够处理更复杂的非结构化任务。

开源AI工作流 工作流的设计遵循"最小配置，最大复用"原则：核心逻辑已经封装好，用户只需配置自己的 API Key 和业务参数即可快速上手。工作流内置错误处理和重试机制，在网络波动或 API 限速等情况下仍能稳定运行，适合作为生产环境的自动化基础设施。

在实际部署时，建议先在测试环境中运行 3-5 次，验证各个环节的输出结果符合预期，再部署到生产环境。AI Skill Hub 评分 7.5 分，是同类 Agent 工作流中的精选推荐。
📋 工具概览

开源AI工作流 是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。

GitHub Stars
⭐ 9
开发语言
Go
支持平台
Windows / macOS / Linux（跨平台）
维护状态
轻量级项目，按需更新
开源协议
Apache-2.0
AI 综合评分
7.5 分
工具类型
Agent工作流
Forks
1
📖 中文文档
以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

开源AI工作流 是一套完整的 AI Agent 自动化工作流方案。通过可视化的节点编排，将复杂的多步骤任务拆解为清晰的自动化流程，实现全程无人值守的智能处理。支持与数百种外部服务和 API 无缝集成，适合构建数据处理管线、业务自动化和 AI 辅助决策系统。

📌 核心特色
  • 可视化 Agent 工作流编排，无需编写复杂代码
  • 支持多步骤自动化任务链，实现全流程无人值守
  • 与外部 API、数据库和第三方服务无缝集成
  • 内置错误处理与自动重试机制，保障稳定运行
  • 提供可复用的自动化模板，快速在同类场景部署
🎯 主要使用场景
  • 自动化日常重复性工作，将精力集中于创造性任务
  • 构建数据采集 → 处理 → 输出的完整自动化管线
  • 实现跨平台、跨系统的数据流转和业务协同
以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。
安装命令
# 方式一：go install（推荐）
go install github.com/Temikus/denkeeper@latest

# 方式二：从源码编译
git clone https://github.com/Temikus/denkeeper
cd denkeeper
go build -o denkeeper .

# 方式三：下载预编译二进制
# 访问 Releases 页面下载对应平台二进制文件
# https://github.com/Temikus/denkeeper/releases
📋 安装步骤说明
  1. 访问 GitHub 仓库获取工作流文件
  2. 在对应平台（Dify / Flowise / Make 等）中找到「导入工作流」功能
  3. 上传工作流文件
  4. 按照提示配置必要的环境变量和 API Key
  5. 运行测试确认流程正常后投入使用
以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。
常用命令 / 代码示例
# 查看帮助
denkeeper --help

# 基本运行
denkeeper [options] <input>

# 详细使用说明请查阅文档
# https://github.com/Temikus/denkeeper
以下配置示例基于典型使用场景生成，具体参数请参照官方文档调整。
配置示例
# denkeeper 配置说明
# 查看配置选项
denkeeper --config-example > config.yml

# 常见配置项
# output_dir: ./output
# log_level: info
# workers: 4

# 环境变量（覆盖配置文件）
export DENKEEPER_CONFIG="/path/to/config.yml"
📑 README 深度解析 真实文档 完整度 74/100 查看 GitHub 原文 →
以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

简介

<p align="center"> <img src="assets/logo_text.png" alt="Denkeeper" width="300"> </p>

<p align="center"> <a href="https://github.com/Temikus/denkeeper/actions/workflows/ci.yml"><img src="https://github.com/Temikus/denkeeper/actions/workflows/ci.yml/badge.svg" alt="CI"></a> <a href="https://github.com/Temikus/denkeeper/actions/workflows/security.yml"><img src="https://github.com/Temikus/denkeeper/actions/workflows/security.yml/badge.svg" alt="Security"></a> <a href="https://github.com/Temikus/denkeeper/releases/latest"><img src="https://img.shields.io/github/v/release/Temikus/denkeeper?label=release" alt="Latest Release"></a> <a href="https://github.com/Temikus/denkeeper/pkgs/container/denkeeper"><img src="https://img.shields.io/github/v/release/Temikus/denkeeper?label=ghcr.io&logo=docker" alt="Docker Image"></a> <a href="https://goreportcard.com/report/github.com/Temikus/denkeeper"><img src="https://goreportcard.com/badge/github.com/Temikus/denkeeper" alt="Go Report Card"></a> <a href="LICENSE"><img src="https://img.shields.io/github/license/Temikus/denkeeper" alt="License"></a> <a href="https://github.com/Temikus/denkeeper/actions/workflows/ci.yml"><img src="https://img.shields.io/badge/UI_coverage-enforced-blue" alt="UI Coverage"></a> </p>

A security-first personal AI agent that lives in your chat. Built in Go as a single binary, designed to run anywhere from a Raspberry Pi to a cloud VM.

Denkeeper connects to your Telegram or Discord, routes messages through LLM providers via Anthropic, OpenAI, OpenRouter, or a local Ollama instance, and remembers conversations across sessions using a local SQLite database. It enforces per-session cost budgets, user allowlists, and a tiered permission system — so you stay in control of what it can do and how much it can spend.

Features

  • Single binary — no runtime dependencies, no containers required
  • Multi-agent routing — run multiple named agents, each with their own persona, skills, LLM model, and permission tier
  • Telegram + Discord — chat with your agent from your phone or Discord server, including inline Approve/Deny buttons for supervised actions; both adapters can run simultaneously
  • User allowlist — only approved user IDs can interact (per-adapter)
  • LLM routing — pluggable provider interface; Anthropic (direct), OpenAI (direct + Azure/vLLM-compatible), OpenRouter (cloud, hundreds of models), and Ollama (local inference) built-in
  • Fallback strategies — automatic model/provider switching on errors, rate limits, or low funds
  • Cost tracking — per-session budgets with automatic cutoff
  • Conversation memory — SQLite-backed, persistent across restarts
  • Scheduler — cron expressions, named intervals, and @daily/@hourly shorthand; per-schedule agent targeting and session modes
  • Skills — flat markdown files with TOML frontmatter; trigger-based filtering (command:/schedule:) and per-agent skill merging
  • MCP tools — spawn MCP servers via stdio (subprocess) or SSE/Streamable HTTP (remote), discover tools, and execute tool calls in an agentic loop; auto-restart on crash with configurable backoff; OAuth 2.1 authorization for remote MCP servers
  • MCP security — SSRF protection (blocks localhost, link-local, and cloud metadata endpoints), HTTP header injection prevention, redirect target validation, env var denylist for secrets, and URL/arg redaction in API responses
  • Plugin system — subprocess and Docker-sandboxed plugins with capability declarations and Ed25519 signature verification; tools capability wires plugin tools into the agent's LLM loop
  • Runtime tool management — add and remove MCP tools and plugins at runtime without restarting; changes are persisted to TOML config
  • Agent KV store — per-agent key-value storage with optional TTL, exposed as MCP tools (kv_get/kv_set/kv_delete/kv_list/kv_set_nx); useful for locks, counters, caches, and cross-session state
  • Supervisor agents — a supervised agent can designate another agent as its supervisor via supervisor = "agent-name" in TOML; the supervisor sits between auto-approve rules and human approval, returning APPROVE/DENY/ESCALATE for each tool call; supervisor prompt includes skill/schedule context for scheduled invocations; configurable timeout (supervisor_timeout, default 30s) and context message count (supervisor_context_messages, default 5); LLM failures emit a supervisor_error event before falling through to human approval
  • Audit log — unified audit trail with buffered emitter, SQLite storage, and 11 event categories (tool_call, skill, channel, approval, schedule, llm, config, session, mcp, safety, supervisor); web UI page with timeline and table views, category/status/agent/time filters
  • Channels — named routing endpoints ([[channels]]) that decouple sessions from adapters; cross-adapter session sharing, ephemeral session mode, /session command for runtime switching; auto-synthesized from agent adapters bindings when absent (backward compatible)
  • Safety commands — /stop cancels the current in-flight request, /panic emergency-stops all in-flight requests and pauses the scheduler, /resume clears panic state; available in Telegram, Discord, web UI, and REST API
  • Session history management — /clear removes all messages from a session, /compact summarises via LLM and replaces all messages with a single summary; available in Telegram, Discord, web UI, and REST API
  • OpenAPI spec — generated via swaggo/swag, served at GET /api/v1/openapi.json (no auth required)
  • Web dashboard — embedded Svelte UI (served via the API server) with 17 pages: overview, chat, sessions, approvals, schedules, skills, tools, browser, KV store, costs, agents, API keys, providers, server config, settings, audit log, and channels; includes dark mode toggle and warm light theme
  • Voice — speech-to-text and text-to-speech via OpenAI (Whisper + TTS)
  • Permission tiers — autonomous, supervised (default), and restricted; configurable per-agent or per-schedule
  • Approval workflows — supervised-tier actions (profile updates, skill creation, schedule additions, tool installation) require explicit human approval via chat buttons (Telegram/Discord) or REST API
  • Config MCP server — per-agent in-process MCP tools let the LLM manage skills, schedules, tools, plugins, KV storage, and inspect its own permission tier at runtime
  • External REST API — HTTP server with scoped API key auth, rate limiting, CORS, and TLS support; chat endpoint with real-time token streaming (SSE + WebSocket), session management, approval CRUD, tool/plugin CRUD, LLM provider management, server reload/restart, and API key management
  • Dashboard authentication — password login (bcrypt), OAuth2/OIDC SSO (PKCE), session cookies (AES-256-GCM)
  • OpenTelemetry observability — Prometheus /metrics endpoint and optional OTLP trace export
  • CLI plugin signing — denkeeper plugin keygen/sign/verify commands for Ed25519 plugin binary signing and verification
  • CLI password hashing — denkeeper passwd generates a bcrypt hash for dashboard password login
  • Personality — ships with a SOUL.md that gives the agent character (editable)

Prerequisites

Installation

Docker

docker pull ghcr.io/temikus/denkeeper:latest
docker run -d --name denkeeper \
  -v ~/.denkeeper:/data \
  ghcr.io/temikus/denkeeper:latest

The container reads config from DENKEEPER_CONFIG (default /data/denkeeper.toml). Override with -e DENKEEPER_CONFIG=/path/to/config.toml.

Setup

```bash

Build and run

just build ./pkg/bin/denkeeper serve 


Or run directly without building:
bash just serve ```

Quick start

Copy and edit the config

mkdir -p ~/.denkeeper cp denkeeper.toml.example ~/.denkeeper/denkeeper.toml

Configuration

Denkeeper uses a single TOML file (default ~/.denkeeper/denkeeper.toml). See denkeeper.toml.example for all options. The config path can be set via --config flag or DENKEEPER_CONFIG env var.

Health check: GET /api/v1/health returns {"status":"ok"} with no authentication required. Use this for Docker HEALTHCHECK or Kubernetes liveness/readiness probes (requires api.enabled = true).

Key sections:

SectionPurpose
[telegram]Bot token and allowed user IDs
[discord]Bot token and allowed user snowflake IDs
[llm]Default provider name, model, and per-session cost limits (cost_limit_soft, cost_limit_hard)
[[llm.providers]]Named provider instances — multiple instances of the same type allowed (e.g. OpenAI + LM Studio)
[llm.anthropic]Anthropic API key — legacy single-slot syntax, auto-converted to [[llm.providers]]
[llm.openrouter]OpenRouter API key — legacy single-slot syntax
[llm.ollama]Ollama base URL — legacy single-slot syntax
[[llm.fallback]]Fallback strategies (error/rate_limit/cost_limit triggers)
[session]Default permission tier (supervised/autonomous/restricted)
[[agents]]Multi-agent definitions (persona, skills, LLM provider/model override, adapter bindings, supervisor, supervisor_timeout, supervisor_context_messages, cost limits)
[[channels]]Named routing endpoints — bind adapter chats to agents with session identity; session_mode (shared/ephemeral)
[audit]Audit log settings (enabled, retention_days, cleanup_interval, buffer_size)
[mcp]Global MCP settings — request timeout, auto-restart, max restart attempts, restart cooldown, SSE URL allowlist
[tools.*]MCP tool server definitions — stdio (subprocess) or SSE (remote) transport, URL, headers, per-server timeout override
[plugins.*]Plugin definitions — subprocess or Docker-sandboxed (capability declarations)
[security]Ed25519 plugin signing config (trusted_keys, allow_unsigned)
[voice]STT/TTS configuration (OpenAI)
[api]External REST API (listen addr, TLS, CORS, rate limiting, API keys with scopes)
[api.auth]Dashboard authentication (bcrypt password, session secret, OIDC SSO)
[otel]OpenTelemetry observability (Prometheus metrics, OTLP trace export)
[[schedules]]Recurring tasks (cron, interval, or named schedules)
[kv]Agent KV store limits (max_keys_per_agent, max_value_bytes, cleanup_interval)
[memory]SQLite database path
[log]Log level and format

Environment Variables

Secrets and select config fields can be set via environment variables, which take precedence over values in denkeeper.toml. This enables the standard Kubernetes pattern of using a ConfigMap for config and a Secret for credentials.

Env VarConfig Field
DENKEEPER_CONFIGConfig file path (replaces --config flag)
DENKEEPER_TELEGRAM_TOKENtelegram.token
DENKEEPER_DISCORD_TOKENdiscord.token
DENKEEPER_LLM_PROVIDERllm.default_provider
DENKEEPER_LLM_MODELllm.default_model
DENKEEPER_LLM_OPENROUTER_API_KEYllm.openrouter.api_key
DENKEEPER_LLM_ANTHROPIC_API_KEYllm.anthropic.api_key
DENKEEPER_LLM_ANTHROPIC_BASE_URLllm.anthropic.base_url
DENKEEPER_LLM_OLLAMA_BASE_URLllm.ollama.base_url
DENKEEPER_LLM_OPENAI_API_KEYllm.openai.api_key
DENKEEPER_LLM_OPENAI_BASE_URLllm.openai.base_url
DENKEEPER_VOICE_OPENAI_API_KEYvoice.openai.api_key
DENKEEPER_LOG_LEVELlog.level
DENKEEPER_LOG_FORMATlog.format
DENKEEPER_MEMORY_DB_PATHmemory.db_path
DENKEEPER_API_ENABLEDapi.enabled (accepts "true" or "1")
DENKEEPER_API_LISTENapi.listen
DENKEEPER_SESSION_TIERsession.tier
DENKEEPER_API_AUTH_SESSION_SECRETapi.auth.session_secret (AES-256 hex key)
DENKEEPER_OIDC_CLIENT_IDapi.auth.oidc.client_id
DENKEEPER_OIDC_CLIENT_SECRETapi.auth.oidc.client_secret
DENKEEPER_API_WEBSOCKET_ENABLEDapi.websocket_enabled (accepts "true" or "false")
DENKEEPER_OTEL_ENABLEDotel.enabled (accepts "true" or "false")
DENKEEPER_OTEL_TRACES_ENDPOINTotel.traces_endpoint (OTLP HTTP endpoint)

A Helm chart is available in deploy/helm/denkeeper/ for Kubernetes deployments.

Fill in your token, API key, and user ID

$EDITOR ~/.denkeeper/denkeeper.toml

REST API

The API server and web dashboard are enabled by default (listening on :8080). All endpoints (except /health) require a Bearer token matching a configured API key.

[api]
listen = "0.0.0.0:8080"

[[api.keys]]
name = "my-client"
key  = "dk-your-secret-key"
scopes = ["chat", "sessions:read", "costs:read"]

Available scopes: chat, admin, agents:read, agents:write, sessions:read, sessions:write, costs:read, skills:read, skills:write, schedules:read, schedules:write, approvals:read, approvals:write, tools:read, tools:write, kv:read, kv:write, channels:read, channels:write, audit:read

Endpoints:

MethodPathScopeDescription
GET/api/v1/health—Health check (no auth)
GET/api/v1/openapi.json—OpenAPI 2.0 spec (no auth)
GET/llms.txt—LLM-readable instance summary: base URL, auth notes, key endpoints, configured agents (no auth)
GET/api/v1/setup—First-run setup status
POST/api/v1/setup—Initialize first-run configuration
POST/api/v1/chatchatSend a message; returns { session_id, response }. Add Accept: text/event-stream for SSE.
GET/api/v1/wschatWebSocket upgrade for bidirectional streaming (auth via ?token= or session cookie)
GET/api/v1/modelsagents:readList available LLM models from all providers
GET/api/v1/models/detailsagents:readModel details with pricing info
GET/api/v1/llm/providersadminList LLM providers with current config
POST/api/v1/llm/providersadminCreate a named provider instance
PATCH/api/v1/llm/providers/{name}adminUpdate provider config (API key, base URL)
DELETE/api/v1/llm/providers/{name}adminRemove a provider instance
PATCH/api/v1/llm/configadminUpdate global LLM config (default provider, model)
GET/api/v1/server/configadminServer config (version, build info, CORS, WebSocket)
PATCH/api/v1/server/configadminUpdate server config (CORS origins, WebSocket settings)
POST/api/v1/server/reloadadminReload config from disk
POST/api/v1/server/restartadminRestart the server process
GET/api/v1/auth/statusadminAuth config summary (password, OIDC, sessions)
GET/api/v1/auth/sessionsadminList active sessions
DELETE/api/v1/auth/sessions/{id}adminRevoke a session
POST/api/v1/auth/passwordadminChange password
GET/api/v1/auth/oidc/testadminTest OIDC provider reachability
POST/api/v1/auth/preferencesadminSet preferred login method
GET/api/v1/onboardingadminSetup checklist status
POST/api/v1/onboarding/dismissadminDismiss onboarding card
GET/api/v1/sessionssessions:readList all conversations
GET/api/v1/sessions/{id}/messagessessions:readGet messages for a session
GET/api/v1/sessions/{id}/statssessions:readSession telemetry summary
GET/api/v1/sessions/{id}/tool-callssessions:readTool call records for a session
GET/api/v1/sessions/{id}/skillssessions:readSkill usage for a session
POST/api/v1/sessions/{id}/clearsessions:writeClear all messages in a session (keeps conversation row)
POST/api/v1/sessions/{id}/compactsessions:writeCompact session into LLM summary
POST/api/v1/sessions/{id}/stopchatCancel in-flight request for a session
DELETE/api/v1/sessions/{id}sessions:readDelete a session and its history
POST/api/v1/panicadminEmergency stop — cancel all in-flight requests, pause scheduler
POST/api/v1/resumeadminClear panic state, resume scheduler
GET/api/v1/panicadminGet panic state ({panicked, panic_time})
GET/api/v1/telemetry/summarycosts:readAggregate telemetry (?since=&until=)
GET/api/v1/agentsagents:readList agents with metadata
POST/api/v1/agentsadminCreate a new agent at runtime
GET/api/v1/agents/{name}agents:readAgent details and skills
PATCH/api/v1/agents/{name}agents:writeMutate agent config (tier, model, supervisor, cost limits)
DELETE/api/v1/agents/{name}adminRemove an agent (rejects if referenced by channels/schedules)
GET/api/v1/skillsskills:readList all skills across agents
GET/api/v1/skills/{agent}skills:readList skills for a specific agent
POST/api/v1/skills/{agent}skills:writeCreate a skill
PUT/api/v1/skills/{agent}/{name}skills:writeUpdate a skill
DELETE/api/v1/skills/{agent}/{name}skills:writeDelete a skill
GET/api/v1/schedulesschedules:readList schedules with run times
POST/api/v1/schedulesschedules:writeCreate a schedule
PATCH/api/v1/schedules/{name}schedules:writeUpdate a schedule
DELETE/api/v1/schedules/{name}schedules:writeDelete a schedule
GET/api/v1/costscosts:readCost summary
GET/api/v1/approvalsapprovals:readList approval requests (filter by ?status=pending)
GET/api/v1/approvals/{id}approvals:readGet a single approval request
POST/api/v1/approvals/{id}/approveapprovals:writeApprove; ?auto_approve=session\|permanent to create auto-approve rule
POST/api/v1/approvals/{id}/denyapprovals:writeDeny a pending request
GET/api/v1/auto-approveapprovals:readList auto-approve rules (filter by ?agent=)
POST/api/v1/auto-approveapprovals:writeCreate an auto-approve rule
DELETE/api/v1/auto-approve/{id}approvals:writeDelete an auto-approve rule
GET/api/v1/keysadminList API keys (secrets not returned)
POST/api/v1/keysadminCreate a new API key
DELETE/api/v1/keys/{id}adminRevoke an API key
DELETE/api/v1/keys/{id}/permanentadminPermanently delete a revoked key
POST/api/v1/keys/{id}/rotateadminRotate an API key
GET/api/v1/toolstools:readList MCP tool servers
GET/api/v1/tools/{name}tools:readGet tool server details
POST/api/v1/toolstools:writeAdd a tool server
PUT/api/v1/tools/{name}tools:writeEdit a tool server
DELETE/api/v1/tools/{name}tools:writeRemove a tool server
GET/api/v1/tools/{name}/healthtools:readTool server health status
POST/api/v1/tools/{name}/restarttools:writeManually restart a tool server
GET/api/v1/pluginstools:readList plugins
GET/api/v1/plugins/{name}tools:readGet plugin details
POST/api/v1/pluginstools:writeAdd a plugin
DELETE/api/v1/plugins/{name}tools:writeRemove a plugin
GET/api/v1/kv/{agent}kv:readList KV keys for an agent
GET/api/v1/kv/{agent}/{key}kv:readGet a KV key value
PUT/api/v1/kv/{agent}/{key}kv:writeSet a KV key value (body: {"value":"...","ttl":"5m"})
DELETE/api/v1/kv/{agent}/{key}kv:writeDelete a KV key
GET/api/v1/channelschannels:readList all channels
POST/api/v1/channelschannels:writeCreate a channel
GET/api/v1/channels/{name}channels:readChannel detail
PATCH/api/v1/channels/{name}channels:writeUpdate a channel
DELETE/api/v1/channels/{name}channels:writeRemove a channel
POST/api/v1/channels/{name}/activatechannels:writeSet active channel for an adapter key
DELETE/api/v1/channels/{name}/activatechannels:writeClear active channel override
GET/api/v1/auditaudit:readList audit events (filter by ?category=&agent=&status=&since=&until=)
GET/api/v1/audit/statsaudit:readAggregate counts by category/status

Chat example:

```bash

🎯 aiskill88 AI 点评 A 级 2026-05-24

denkeeper是一个开源的AI工作流，提供了一个单一二进制的个人AI代理，用户可以自定义控制AI工作流，具有很好的可扩展性和可定制性。

📚 实用指南（长尾问题）
适合谁
  • 需要让 Claude / Cursor 操作本地工具的 AI 工程师
  • 构建多智能体协作系统的 Agent 开发者
  • 做语音类 AI 产品的开发者
最佳实践
  • 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
  • 生产部署优先使用 Docker Compose 隔离依赖，并挂载 volume 持久化数据
  • 本地部署优先选 GGUF 量化模型，节省显存并保持响应速度
  • Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
常见错误
  • API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
  • MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
  • 容器内无法访问宿主机 localhost — 使用 host.docker.internal
  • 显存不足直接 OOM — 优先降低 context 或换更小的量化模型
部署方案
  • Docker：denkeeper 提供官方镜像，docker compose up 一键启动
  • CLI：直接 npm install -g / pip install，命令行调用
  • 本地部署：CPU 8GB 起，GPU 推荐 16GB+ 显存
  • 云端托管：可放在 Vercel / Railway / Fly.io 等 PaaS 平台
相关搜索
denkeeper 中文教程denkeeper 安装报错怎么办denkeeper MCP 配置denkeeper Docker 部署denkeeper Agent 工作流denkeeper 与同类工具对比denkeeper 最佳实践denkeeper 适合谁用
⚡ 核心功能
👥 适合谁
  • 需要让 Claude / Cursor 操作本地工具的 AI 工程师
  • 构建多智能体协作系统的 Agent 开发者
  • 做语音类 AI 产品的开发者
⭐ 最佳实践
  • 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
  • 生产部署优先使用 Docker Compose 隔离依赖，并挂载 volume 持久化数据
  • 本地部署优先选 GGUF 量化模型，节省显存并保持响应速度
  • Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
⚠️ 常见错误
  • API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
  • MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
  • 容器内无法访问宿主机 localhost — 使用 host.docker.internal
  • 显存不足直接 OOM — 优先降低 context 或换更小的量化模型
👥 适合人群
自动化工程师和运维人员项目经理和业务分析师希望减少重复性工作的专业人士数字化转型团队
🎯 使用场景
  • 自动化日常重复性工作，将精力集中于创造性任务
  • 构建数据采集 → 处理 → 输出的完整自动化管线
  • 实现跨平台、跨系统的数据流转和业务协同
⚖️ 优点与不足
✅ 优点
  • +Apache-2.0 协议，可免费商用
  • +大幅减少重复性人工操作
  • +可视化流程，清晰直观
  • +可扩展性强，支持复杂场景
⚠️ 不足
  • −初始配置和调试需投入一定时间
  • −强依赖外部服务的稳定性
  • −复杂场景需具备一定技术基础
⚠️ 使用须知

AI Skill Hub 为第三方内容聚合平台，本页面信息基于公开数据整理，不对工具功能和质量作任何法律背书。

建议在沙箱或测试环境中充分验证后，再部署至生产环境，并做好必要的安全评估。

📄 License 说明

✅ Apache 2.0 — 宽松开源协议，可商用，需保留版权声明和 NOTICE 文件，含专利授权条款。

🔗 相关工具推荐
LangChain AI开发框架
Agent工作流
ai-agents-for-beginners Agent工作流
微软官方开源项目，提供12堂系统课程学习AI智能体框架。涵盖工作流设计、RAG检索增强、多智能体协作等核心技能。适合AI
n8n AI工作流自动化
Agent工作流
LangFlow 可视化AI开发
Agent工作流
📰 相关 AI 新闻
AI Agent 自主化能力最新进展
AI 资讯 · 知识关联
GitHub热门：claude-mem — Persistent Context Across Sessions for Every Agent – Capt
AI 资讯 · 知识关联
OpenAI 最新产品与研究动态
AI 资讯 · 知识关联
AI Agent 自主化能力最新进展
AI 资讯 · 知识关联
🍿 AI 圈相关吃瓜
AutoGPT 自主完成了任务：把我的文件夹全部重命名了
AI 圈观察
配了5个 MCP 工具，Claude 一个都没用
AI 圈观察
Filesystem MCP 帮 Claude 找文件，找了整个 node_modules
AI 圈观察
🗺️ 相关解决方案
mcp
mcp-server-setup
agent
ai-agent-workflow
workflow
ai-workflow-templates
docker
docker-deploy
🧩 你可能还需要
基于当前 Skill 的能力图谱，自动补全的工具组合
技能寻求者
MCP · Agent · 工作流
natively-cluely-ai-assistant — Claude Skill 中文使用文档
免费开源的AI面试助手，实时转录，隐蔽模式，局部RAG，BYOK。无订阅，防止数据泄露。
DeepCode Agent工作流
MCP · Agent · 工作流
开源AI工具：RAG知识库系统
基于Vue.js前端的RAG知识库系统，提供高效的知识检索和生成功能，助力AI应用开发
CrewAI 多代理协作平台
MCP · Agent · 工作流
LEANN AI技能包
MCP · Agent · 工作流
❓ 常见问题 FAQ
解答
💡 AI Skill Hub 点评

经综合评估，开源AI工作流 在Agent工作流赛道中表现稳健，质量良好。如果你已有明确的使用需求，可以直接上手体验；如果还在评估阶段，建议对比同类工具后再做决策。

⬇️ 获取与下载
⬇ 下载源码 ZIP

✅ Apache-2.0 协议 · 可免费商用 · 直接从 aiskill88 服务器下载，无需跳转 GitHub

📚 深入学习 开源AI工作流
查看分步骤安装教程和完整使用指南，快速上手这款工具
⚙️ 安装教程 📚 使用教程
🌐 原始信息
原始名称 denkeeper
原始描述 开源AI工作流：A single-binary personal AI agent designed for people who want full control over。⭐9 · Go
Topics workflowgo
GitHub https://github.com/Temikus/denkeeper
License Apache-2.0
语言 Go
🔗 原始来源
🐙 GitHub 仓库  https://github.com/Temikus/denkeeper 🌐 官方网站  http://denkeeper.io/

收录时间：2026-05-19 · 更新时间：2026-05-19 · License：Apache-2.0 · AI Skill Hub 不对第三方内容的准确性作法律背书。