ang-XWBWZ/dsh-approval-ai

@llangtop/dsh-approval-ai

English | 中文

AI approval answerer for approval/request. DSH creates and routes the approval request; this plugin only answers that already-created request with a minimal ctx.llm assessment. It adds no path, workspace, shell, sandbox, or risk trigger of its own. The default route is provider deepseek-official with model deepseek-v4-flash; the adapter owns credentials and provider protocol.

Configuration

- id: approval-ai
  name: '@llangtop/dsh-approval-ai'
  config:
    provider: deepseek-official
    model: deepseek-v4-flash
    mode: ai-only
    currentPath: /workspace/project
    projectArchitecture: 'Configuration-supplied summary; the plugin never reads project files.'
    implementationArchitecture: 'Approval policy plugin over approval/request and ctx.llm.'
    agentsMd: 'Configuration-supplied guidance; the plugin never reads AGENTS.md.'
    securityApprovalPrompt: 'Assess only this approval request; do not read files or call tools.'
    timeoutMs: 3000
    failClosed: true

mode is ai-only, ai-then-human, or human-only. The plugin receives every approval request that reaches its listener; it does not decide whether an approval request should exist. human-only delegates every request. ai-only maps valid allow assessments to allowed-once; deny, high/critical risk, review, malformed output, missing routes, cancellation, timeout, and provider errors fail closed. ai-then-human maps review to the configured reviewOutcome because listener order is not a priority mechanism.

Page operations

In the Web composition, the client bundle contributes a card to the native settings page and the host registers the approval-ai settings namespace. The card can be used at Settings → Plugins → Plugin configuration → AI Approval when the DSH Web settings API exposes that namespace; Save writes the namespace, Discard drops page-local edits, and Reset removes user overrides. Version 0.1.0-rc.5 did not include the client card, so install 0.1.0-rc.6 or later and restart Web after updating the profile.

The current DSH Web host filters settings namespaces through a fixed allowlist before /api/settings.describe responds. approval-ai is registered by this plugin but is not currently in that host allowlist, so the expected result can be that the package is installed and the client bundle is loaded while the settings card is absent. This is a host API exposure limitation, not a slot-order, npm-scope, or client-export problem. A third-party package cannot add a namespace to the fixed host allowlist by itself; use /approval-ai below until the host provides an extensible settings registration mechanism.