AgentDash

AgentDash companion interaction protocol. Use when an AgentDashboard session needs companion_request/companion_respond to ask a human, request platform capability grants, coordinate parent/sub-session work, return structured review or completion results, or route model-authored dynamic workflow proposals such as research fanout, review pipelines, runbooks, and local-effect workflows through human/platform review before execution.

Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed spec refresh, cross-session memory (trellis mem) generated by trellis init, or AI-facing bundled skills (trellis-channel, trellis-session-insight, trellis-spec-bootstrap) and bundled-skill auto-dispatch flow.

Required guide for AgentDashboard Canvas work. Read this first when the user asks to use Canvas, create or modify a Canvas surface, or show information to the user through a visual/workspace panel; it defines the canonical Canvas workflow, VFS authoring boundary, preview/present/inspect operations, data binding, runtime bridge, and user-visible delivery rules.

AgentDashboard workspace module operating guide. Use when a session has workspace_module tools, when creating, attaching, or copying Canvas modules, when invoking or presenting workspace modules, or when deciding whether to use workspace_module_operate, workspace_module_list, workspace_module_describe, workspace_module_invoke, or workspace_module_present.

Manage ProjectAgent long-term memory in the default agent:// VFS home. Use when reading, creating, or updating MEMORY.md and topics/*.md so durable memory stays concise, verified, secret-free, and maintained with normal VFS file tools.

AgentDashboard Routine memory protocol. Use when a session is started by a scheduled, webhook, or plugin-triggered Routine and has a routine:// VFS mount; read trigger facts and durable Routine/entity memory for cross-trigger continuity, then update only concise future-use facts, decisions, open items, or entity outcomes.