@agentled/cli 0.7.21 → 0.8.0

package/patterns/v1/08-composed-email-approval.md

@@ -47,7 +47,7 @@ Sender identity lives on a workflow-level `inputPages` entry with `contextKey: "
   "name": "Send Outreach Email",
   "pipelineStepPrompt": {
     "type": "email",
-    "template": "Draft a personalized email to {{steps.enrich.contact.fullName}} at {{steps.enrich.company.name}} introducing our offering. Keep it warm, concise, and specific to their role.",
+    "template": "Draft a personalized email to {{steps.enrich.contact.fullName}} at {{steps.enrich.company.name}} introducing our offering. Keep it warm, concise, and specific to their role. Format the body as email-safe HTML with one <p> per visual paragraph.",
     "responseStructure": {
       "email": {
         "from": "{{context.outreachProfile.fromEmail}}",
@@ -109,6 +109,10 @@ pipelineStepPrompt:
 
 Email clients render HTML bodies literally if the wrapping element is missing. Always generate email-safe HTML (`<p>`, `<br>`, `<a>`, `<strong>` — no CSS blocks, no `<script>`). Don't use markdown — the approval UI won't convert it.
 
+**Email body as one collapsed paragraph:**
+
+Email clients collapse newline-only text, so a body like `Hi Alberto, Quick confirmation... Best, Ouadie` renders as one hard-to-read block. Use separate `<p>` blocks for the greeting, each paragraph, links/CTA, and sign-off. Prefer `<a href="...">descriptive link text</a>` for long URLs instead of pasting raw links into the middle of a sentence.
+
 **No `outreachProfile` input page:**
 
 `{{context.outreachProfile.fromEmail}}` resolves to an empty string. The email has no sender. It may still send (from the default connected account) but you lose per-workflow sender control.
@@ -124,6 +128,7 @@ Before wiring a composed-email step into a workflow:
 - [ ] `onApproval.action: "schedule-email"` is set
 - [ ] `next.conditions.approvalRequired: true` on the outgoing edge
 - [ ] Recipient and subject are derived from prior step output, not hardcoded
+- [ ] `email.body` is readable email-safe HTML with separate paragraphs; it is not one plain-text block and does not rely on newline-only formatting
 - [ ] The output page has `displayConfig.executionNameTemplate` with the entity and outreach state. For single-entity outreach, use `{{entityName}} - Email Drafted` before approval and `{{entityName}} - Email Sent` or `{{entityName}} - Contacted` after the post-send status step, e.g. `Joe Dan - VC Firm Name - Email Drafted`; add `{{today}}` only when a short date helps. For batch runs, summarize counts instead, e.g. `26 May - 4 sourced - 3 contacted`.
 
 ## When to use a generic approval gate instead

package/skills/agentled/SKILL.md

@@ -27,6 +27,7 @@ them; that defeats the point.
 | Sourcing/collecting entities to act on later | `references/entity-pipeline.md` |
 | Adding cross-execution memory | `references/persistent-memory.md` |
 | Designing outbound / sales / investor / lead-gen at scale | `references/outreach-and-scale.md` |
+| Designing a saved view of a list, funnel, queue, approvals surface, or multi-source workspace cockpit | `docs/WORKSPACE_VIEWS.md` |
 | Producing local artifacts, or seeding a templated workspace's sidebar | `references/workspace-folder.md` |
 | Picking apps, testing credit-efficiently, decoding a validation error | `references/credits-apps-and-errors.md` |
 
@@ -62,13 +63,34 @@ Before helping with any request, inspect the workspace. Use `agentled workspace
 4. **`list_knowledge_lists`** — KG lists: contacts, companies, scored leads, status machines. Shapes what a new workflow reads from or writes to.
 5. **`list_connections`** — Connected apps and integrations: know which enrichment, CRM, or email providers are already authed before designing steps that depend on them.
 6. **`list_agents`** — Existing agents and routines: understand what is already running autonomously before adding new agents.
+7. **`list_workspace_views`** — Saved operating surfaces: reuse or update a view before creating another dashboard/list/queue.
 
 The workspace inspection directly informs which integrations are connected, what KG lists exist, whether new workflows should chain from or replace existing ones, and what existing agents already cover.
+When referring to KG lists or text entries in user-facing replies, include both the human-readable name/title and the stable key/id, not just the id. Example: `VC Contacts (gtm_vc_contacts)`.
 
 For existing workflow work, map the workflow back to its use case before making claims or edits: run `agentled workflows get <workflowId> --format json`, inspect `useCaseContext`, then run `agentled use-cases get <key-or-workflowGraphId> --format json` and read each `operatingGuides` knowledge text with the provided read command. If `agentGuidance.warnings` includes `MISSING_USE_CASE_OPERATING_GUIDE`, say the use-case README is missing and create/update the linked knowledge text before treating the context as complete.
 
 > **Shortcut:** `agentled workspace inspect --json` returns all six contexts as one consolidated response. Use it at session start to load the full picture in a single call.
 
+### Workspace views
+
+When the user asks for a reusable view of a KG list, funnel, action queue,
+approval inbox, workflow report, agent/routine state, or combined operating
+surface, use `WorkspaceView`. It is a saved manifest over live workspace data,
+not a KG-only report and not an action executor.
+
+- Inspect existing views first: `list_workspace_views` or `agentled views list`.
+- Create/update only the manifest: data sources, filters/transforms,
+  `ConfigLayout` layout, actions, refresh/safety metadata.
+- Use `name` for the full view page title and `navLabel` for short sidebar
+  copy. Use `placement` to attach pinned views to a use case or workflow group.
+- Creating a view must not read providers, run workflows, mutate KG rows, send
+  messages, make approval decisions, or spend credits.
+- Mark write/send/destructive actions with `approvalRequired: true` and use the
+  normal approval-aware tool when the user later asks to execute them.
+- Prefer `draft` unless the user clearly approved the view becoming active or
+  pinned.
+
 ### MCP-connected but no local scaffold: expected behavior
 
 If MCP tools are already connected and working, **do not block** on missing local folders.
@@ -119,6 +141,29 @@ agentled --workspace angelhive workspace inspect
 AGENTLED_WORKSPACE=angelhive agentled workflows list
 ```
 
+### CLI chat workflow handoffs
+
+The web UI can call `monitorWorkflowExecution`, poll the resulting job, and
+continue the assistant turn after the workflow becomes terminal. A CLI agent
+must perform that continuation itself.
+
+If `agentled chat` or `agentled chat-result` says a workflow was started, do
+not treat the completed chat turn as the completed user request. Capture the
+returned `sessionId`, `workflowId`, `executionId` or `executionInputId`, then:
+
+1. Resolve the execution with `agentled executions list <workflowId>` when
+   necessary.
+2. Poll `agentled executions get <workflowId> <executionId>` until `completed`,
+   `failed`, `stopped`, or `canceled`.
+3. Inspect the relevant output using `agentled executions step-output`.
+4. Continue the original conversation with `agentled chat --session-id
+   <sessionId> "...terminal result context..."` so the assistant reports the
+   verified result and does not restart the workflow.
+
+Never resend the original request while its durable chat turn or workflow is
+still running. A response such as `Run started` is a workflow handoff, not the
+final answer.
+
 ### External builder setup
 
 When this session is acting as an external AI builder for Agentled work items,

package/skills/agentled/references/email-workflows.md

@@ -73,7 +73,7 @@ When a workflow sends emails, add an outreach profile input page to `context.inp
   "name": "Send Email",
   "pipelineStepPrompt": {
     "type": "email",
-    "template": "Draft a personalized email...\n{{steps.previous_step.data}}\nReturn JSON ONLY per schema.",
+    "template": "Draft a personalized email...\n{{steps.previous_step.data}}\nFormat the body as email-safe HTML with one <p> per visual paragraph.\nReturn JSON ONLY per schema.",
     "responseStructure": {
       "email": {
         "from": "{{context.outreachProfile.fromEmail}}",
@@ -118,5 +118,6 @@ When a workflow sends emails, add an outreach profile input page to `context.inp
 - `onApproval.action: "schedule-email"` — triggers the actual send; without it, approval does nothing
 - `next.conditions.approvalRequired: true` — blocks the pipeline until human approval
 - Email body must be email-safe HTML (`<p>`, `<br>`, `<a>`, `<strong>` — no CSS, no scripts)
+- Preserve readable email structure in `email.body`: use separate `<p>` blocks for the greeting, each paragraph, links/CTA, and sign-off; do not return the whole email as one plain-text paragraph, and do not rely on newline-only formatting because email clients collapse it.
 - **Never** use separate "draft" + "gmail send" appAction steps for outreach
 - Set an output page `displayConfig.executionNameTemplate` that names the entity and the outreach state. For single-entity outreach, use `{{entityName}} - Email Drafted` before approval and `{{entityName}} - Email Sent` or `{{entityName}} - Contacted` after the post-send status step, e.g. `Joe Dan - VC Firm Name - Email Drafted`; add `{{today}}` only when a short date helps. For batch runs, summarize counts instead, e.g. `26 May - 4 sourced - 3 contacted`.

package/skills/agentled/references/step-schemas.md

@@ -87,7 +87,7 @@ AI steps can optionally specify a model and provider via the `agent` field:
 | `anthropic` | `claude-4-6-sonnet`, `claude-4-5-haiku`, `claude-4-6-opus` |
 | `google` | `gemini-3-pro`, `gemini-3-flash`, `gemini-2.5-pro`, `gemini-2.5-flash` |
 | `mistral` | `mistral-large-latest`, `mistral-small-latest`, `codestral-latest` |
-| `deepseek` | `deepseek-chat`, `deepseek-reasoner` |
+| `deepseek` | `deepseek-v4-flash`, `deepseek-v4-pro` (`deepseek-chat` and `deepseek-reasoner` are legacy aliases retiring 2026-07-24) |
 | `kimi` | `kimi-k2.5` |
 | `minimax` | `minimax-m2.5` |
 | `bytedance` | `doubao-seed-1.6-flash`, `seed-2.0-mini`, `doubao-seed-1.8-beta` |