description: "Feishu-backed personal-assistant profile bundle for dsh: one 24私助 preset carrying the full standard tool base plus a SQLite-by-default ledger, seven business workers, task skills, voice digests, calendar-native reminders, handwriting review, and a staged access-setup wizard." kind: "package-bundle"

@benz-ai-x/dsh-24pa

English | 中文

Summary

Install @benz-ai-x/dsh-24pa into a Profile to gain the「24私助」assistant preset and its host plugin: a Feishu plus local dual-entry coordinator delegating to seven business workers over a SQLite-by-default ledger (workspace data/pa24.db; optional PostgreSQL) for items, handwritten-note review, digests, and delivery receipts. Behavior ships as task skills — built-in plus workspace-customizable (<workspace>/.dsh/skills/, hot-reloaded), each declaring a deterministic template track or a model-executed track — covering voice digests and calendar-native clock reminders that fire from the Feishu/WeCom app with the host offline. The preset carries the standard-mode tool base restricted per role, so the local session programs while the Feishu entry and workers keep business-only whitelists. Versions follow the dsh baseline (<dsh version>.<serial>) and support dsh 0.2.0-rc.2, 0.2.1-alpha.1–0.2.1-alpha.5, 0.2.1-rc.1–0.2.1-rc.2.

FAQ

What is 24私助 (24PA)? — A Feishu personal-assistant plugin for dsh, shipped as a profile bundle: local dsh sessions and a Feishu bot coordinate seven business workers over a SQLite-by-default ledger — tasks, calendar, memos, digests, handwriting review, and a skill runner — while clock-type reminders ride native calendar events.

Which dsh runtimes are supported? — dsh 0.2.0-rc.2, 0.2.1-alpha.1–0.2.1-alpha.5, 0.2.1-rc.1–0.2.1-rc.2; versions are named <dsh baseline>.<serial> and npm dist-tags track baselines.

How do I install it? — dsh plugin --profile <name> add @benz-ai-x/dsh-24pa@<baseline serial>, then restart the profile (see Installing the Bundle).

Do reminders require the model to be online? — No. Clock-type reminders are written as calendar events with native app alerts (Feishu or WeCom, per calendarChannel) — they fire with both the model and the 24私助 host offline; the ledger keeps a delegated backup row. Follow-up and conditional reminders run as agent-track skills.

Can I add or change routines without touching plugin code? — Yes: periodic tasks, worker personas, access wizards, and workflows all ship as task skills. Drop a <name>.md into the workspace .dsh/skills/ directory (picked up hot) or rebind from the panel's plan cards; each skill declares a deterministic template track or a model-executed track with completion criteria, and can only tighten — never loosen — tool permissions.

How do I connect Feishu? — Tell the local 24私助 session「帮我接通飞书」; the built-in wizard (pa24_connection guide, and check with nextSteps) walks app creation, authorization, resource ids, and health checks. The Feishu entry session can also run this read-only wizard and wecom_guide/wecom_check for channel diagnostics; configuration writes stay local-only (ADR-0001).

Table of Contents

• Use this package
• Understand the implementation
• Further Exploration
• Model Experience
• Known Limitations and Deferred Work
• Dev Note

Use this package

Installing the Bundle

Pick the release matching your dsh runtime, then restart the Profile. The reconcile step activates the patch layer (one assistant preset row plus the host plugin row) for exactly this dsh.bundle declaration.

# dsh 0.2.1-alpha.1 host (schedule service built in)
dsh plugin --profile <name> add @benz-ai-x/dsh-24pa@0.2.1-alpha.1.6

# dsh 0.2.1-alpha.2 – 0.2.1-rc.2 hosts (peers span these baselines; rc.2 is the active release line)
dsh plugin --profile <name> add @benz-ai-x/dsh-24pa@0.2.1-rc.3.1

# alpha.2 – alpha.5 hosts may also pin the alpha line (frozen at 0.2.1-alpha.5.1; preset content identical, only engines/peer range and docs differ)
dsh plugin --profile <name> add @benz-ai-x/dsh-24pa@0.2.1-alpha.5.1

# dsh 0.2.0-rc.2 host — line frozen at 0.2.0-rc.2.3, no further releases (also add the two schedule companions for digests)
dsh plugin --profile <name> add @benz-ai-x/dsh-24pa@0.2.0-rc.2.3
dsh plugin --profile <name> add @deepseek-ai/dsh-experimental-schedule-bundle
dsh plugin --profile <name> add <rc.2 harness checkout>/packages/schedule/schedule

dsh plugin --profile <name> remove @benz-ai-x/dsh-24pa

Removal withdraws the preset and host plugin on the next Profile start; PostgreSQL data, dsh sessions, and the workspace directory are untouched. Version naming follows <dsh baseline version>.<serial>; npm dist-tags track baselines (dsh-0.2.0-rc.2, dsh-0.2.1-alpha.1, dsh-0.2.1-alpha.2, dsh-0.2.1-alpha.5, dsh-0.2.1-rc.1, dsh-0.2.1-rc.2).

Configuration

Secrets live only in the server environment; the workspace AGENTS.md holds one machine-checked JSON block with variable names, revalidated on reload — a bad block never replaces the effective configuration.

AGENTS.md fields: mode (demo/feishu), storage (sqlite/postgres, default sqlite — the ledger is the workspace data/pa24.db file; SQLite uses the built-in node:sqlite, unflagged across this package's supported Node range; postgres requires pgDsnEnv and an external database), larkProfile, ownerOpenId, folderToken, wikiNodeToken (optional — memos and handwriting review docs land under this Feishu wiki node when set; empty falls back to folderToken), tasklistId, calendarId, calendarChannel/todoChannel/notifyChannel (feishu|wecom, default feishu — WeCom as the second operation channel for calendar/todo plus one-way reminder push, never inbound), timeZone, appIdEnv/appSecretEnv/pgDsnEnv, maxWorkers, enabledWorkers, workerModels, extraBusinessSkills (kebab-case allow list releasing workspace business skills to model-driven runs), tts (engine none/melo/volcengine, voice, volcKeyEnv, meloDir — voice digests via cloud Doubao TTS or local Melo), extraLocalTools (subagent_codex, subagent_claude_code, and QwenNote minutes tools via mcp__qwennote__* wildcard or precise names; entries naming unmounted tools are filtered out with a health note). For Feishu access setup, tell the local session「帮我接通飞书」or call pa24_connection with action=guide; the bundled feishu-setup.md is the single authority.

Registered calendars (Manticore / M03)

The Calendar card (日程) reads saved observations; Verify calendars explicitly reads the platforms. In Parameter configuration → Calendar & todo sources, register each personal, company or project calendar, choose its visible scope, creation default, project/company mapping and optional meeting duration. Registration does not grant platform permissions. Conversations query all enabled registered calendars; creation selects one explicit source, mapping or default. Missing or ambiguous targets require clarification.

The sources object in the same AGENTS.md config block is authoritative. Without it, existing calendar/task-list fields yield stable migration candidates. Saving the source editor materializes those candidates; changing a legacy default through the form preserves the old source and adds the new default. An explicit empty registry stays empty. After a registry exists, change defaults there. Removing a source preserves remote objects and operation history. Pending operations retain their original identity and resource; an unknown result is never replayed as a new create.

Feishu reads native instances plus paginated participant/group evidence. WeCom currently uses the authorized scope and a ±30-day window; a named calendar container, complete organizer evidence, invite and personal-reminder edit remain adapter gaps, reported explicitly. WeCom changes require the original confirmed creation receipt. Actual device notification delivery needs real-account verification. Todo sources can be registered/checked in M03; todo operations continue using the existing channel and task-list settings until M04.

Schema 20 adds source registrations, access evidence, platform objects, per-source observations and memberships to both ledgers. Stop the host and keep a joint pre-upgrade backup of the ledger, workspace identity/config and native session history. Restore the whole backup with the matching code to roll back; do not drop migration records or run old and new hosts against the same ledger. See the initialization guide for recovery steps.

Exposing the tool

External CLI delegation rows ship enabled but stay dormant: subagent_codex and subagent_claude_code mount only after their provider bundles (@deepseek-ai/dsh-subagent-codex / -claude-code) are installed into the Profile, and the workspace must then opt in through extraLocalTools; entries naming tools that are not live are filtered before tools.restrict() runs and surface in maintenance health, so a missing provider or channel never breaks agent creation. QwenNote minutes tools pass the same gate from the host plane: add a dsh-mcp-client entry with serverName: qwennote (stdio + mcp-remote OAuth bridge, pinned version) to the Profile patch, complete the owner-browser authorization once, then opt in via mcp__qwennote__*. ralph is available to local sessions and follows its own tool contract: only on an explicit user request.

What you get

• The「24私助」preset: standard plugin set (platform shell, fs, search, jobs, skill, skill-filesystem, tool-skill, goal, plan-mode, compaction, delegation, ask-user, todo, web, present, ralph) plus pa24-agent; persona text merged into the assistant identity; tool-schedule deliberately excluded — clock-type reminders ride native calendar events, with the ledger as backup record.
• Role-restricted tool surfaces: local sessions get the full standard base plus all pa24_* tools; the Feishu entry session and workers keep business-only whitelists (one preset never implies one permission set).
• The host plugin: fixed Feishu access and local sessions, pa24_delegate/pa24_jobs/pa24_notes/pa24_memory/pa24_maintenance/pa24_workspace/pa24_connection/pa24_work, the SQLite-by-default ledger (optional PostgreSQL) with outbox delivery, the task-skill runtime (built-in plus workspace .dsh/skills/), calendar-native clock reminders, voice-capable digests, handwriting review cards, backup/health, the web panel (whose System category carries a parameter-configuration form: validate → rewrite the AGENTS.md config block → reload, with chat and the form sharing one config source; secrets are written via the Secrets group into a 0600 workspace store — write-only in the UI, env vars become optional overrides, and AGENTS.md/system prompts/backups never contain secret values), with workspace binding, switching, AGENTS.md reload, effective-config review, and health & budget living on the panel's System category under the Workspace & config card. WeCom access setup follows the bundled wecom-setup.md via pa24_connection action=wecom_guide / wecom_check.

Failure and recovery

Digests and meeting prep on a dsh 0.2.0-rc.2 host report「当前 Host 未提供原生 Schedule 服务」until the schedule companions above are installed; the registry dsh-schedule@0.2.0-rc.1 is peer-incompatible and its row stays disabled. An uninstalled external CLI provider keeps its tool absent rather than erroring. A second active pa24 Host against the same $DSH_HOME/24pa refuses startup by lock. A fresh Profile ships an unresolved allowBuilds placeholder for protobufjs (a transitive dependency of the Feishu SDK), so the first install exits nonzero until you set it to true in the Profile pnpm-workspace.yaml; the package is fully added either way. A lark-cli timeout settles as result-unknown — verify the real Feishu object before retrying; nothing is blindly re-executed.

Understand the implementation

Further Exploration

Read these pages when the package-level contract is not enough. They move from this bundle to the product it implements and the platform it plugs into.

• Agent guide — task-specific reading paths and repository conventions.
• Product baseline — how the approved Manticore targets relate to the v1 spec and delivery evidence.
• Product spec — v1 stories, scenarios, and test groups.
• Overall design — flows, session topology, and confirmed trade-offs.
• ADR-0001 — the workspace/session permission boundary this preset enforces.
• Research records — per-feature verified contracts, including the dual-baseline and access-wizard studies.
• Delivery plan — feature groups and their dependencies.
• Delivery workflow — branch reuse, dependency checks, acceptance evidence, and merge criteria.

Model Experience

Assistant request

What the model sees

pa24-agent injects four ordered lead sections (identity and capability split, coordination, business domains, safety and reporting) plus the merged persona line; the workspace-rules section (order 910) carries AGENTS.md prose and stays empty until a workspace is bound. Workers receive four-part personas (职责/完成标准/边界/输出要求) instead.

Verbatim identity line (src/prompts.ts)

统一提供助理协调、工作区维护和完整编程能力；按本会话实际可用的工具办理（身份与工作目录见系统提示开头）。

Token effect

Fixed per role after workspace bind; the workspace-rules section is conditional (empty until bound) and is replaced, not extended, on reload.

KV Cache effect

Stable repeated prefix within a session: an AGENTS.md reload replaces the rules section and invalidates reuse from that request on, while a PROMPTS_VERSION bump invalidates across deployments. Nothing else in this bundle rewrites the earlier prefix.

Role-restricted tool catalog

What the model sees

Eight pa24_* schemas with fixed JSON parameters, plus the role restriction applied to the inherited catalog: the Feishu entry sees exactly its five business tools, workers exactly pa24_work and read-only pa24_memory, local sessions the full standard base plus all pa24_* tools.

Token effect

Fixed catalog per role for the session lifetime; extraLocalTools extends the local allow list only, and host-plane additions from other bundles (for example schedule_*) are outside this bundle's allow list.

KV Cache effect

Append-only: the catalog is constant across one session's requests, so conversation growth never rewrites the prefix; changing the workspace extraLocalTools, the preset composition, or upgrading the package invalidates reuse.

Indirectly, through the preset rows this bundle composes, each inserted standard package owns its own tool descriptions and prompt contributions.

Known Limitations and Deferred Work

These limits define when this assistant needs special operational care. They are current package constraints, not a general Feishu comparison or a task backlog.

• Real-tenant operation is single-instance so far — long-connection, identity, and renewal paths now run on one production Feishu tenant (WeCom channels and voice digests included); broader tenant and zone compatibility remains untested, and console permission scope names are keyword-based pending on-console verification.
• Handwriting recognition quality is unquantified — multi-page transcription fidelity needs a 30–50 page real-sample evaluation before any accuracy claim; the visual route must be configured in workerModels.
• dsh 0.2.0-rc.2 hosts ship no schedule service — digests and meeting prep stay honestly unavailable until the schedule companions are installed, and the host-plane schedule_* tools those companions add cannot be hidden by preset restriction.
• External CLI delegation is dormant by default — subagent_codex/subagent_claude_code mount only after their provider bundles are installed and extraLocalTools opts in; unconfigured tools stay absent rather than erroring.
• One writer per state directory — a second active pa24 Host against the same $DSH_HOME/24pa refuses startup by lock; run one host per state directory.

Dev Note