Skip to content

AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).

fix(ui): call the Jobs page "Workflows" (#194)

Rufusd3e48cbc9558
diff --git a/packages/core/openexecutive/guide/prebuilt/ask_oe.json b/packages/core/openexecutive/guide/prebuilt/ask_oe.json
index 0db8e9d6..0ff2199b 100644
--- a/packages/core/openexecutive/guide/prebuilt/ask_oe.json
+++ b/packages/core/openexecutive/guide/prebuilt/ask_oe.json
@@ -1,7 +1,7 @@
{
"section_id": "ask_oe",
"title": "Ask OE",
- "markdown": "**What it is:** A page-aware assistant panel docked on the right of every screen (except the chat home, which *is* the chat). Open it with the **Ask OE** button in the top bar or **Ctrl/Cmd + .** — it's the same Executive you talk to in chat, but it knows what page you're looking at.\n\n**What it does:**\n\n- **Explains the current page.** Ask \"what does this page do?\" or \"what does authority scope mean?\" and the answer is grounded in this guide's section for the page you're on.\n- **Fills forms for you.** On a screen with a form (the workflow builder, the Add-person dialog, the company profile), describe what you want in plain language and the suggested values land directly in the form, highlighted so you can see what came from the Executive.\n- **You always click Save.** Ask OE never submits a form. Suggested values are just that — review them, edit anything, and save through the form's normal button. An **Undo** on the proposal card restores what was there before, and a highlight clears the moment you edit that field yourself.\n\n**How to use:**\n\n1. On any page, click **Ask OE** in the top bar or press **Ctrl/Cmd + .** (press it again to close).\n2. Ask about the page — \"what's the difference between Flag and Reject here?\" — or, on a form page, describe what you want filled in.\n3. Check the highlighted fields. Edit anything that's off, then click the form's own **Save** / **Create** button. Click **Undo** on the proposal card to put the form back as it was.\n4. Click **New conversation** in the panel header to start fresh.\n\n**Where it works:** every page inside the app shell. Form-filling is wired into the workflow builder (**Jobs → + New workflow**), the **Add person** dialog, and the **Company profile**; other pages get the explain tier, with form support arriving screen by screen.\n\n**Example:** on **Jobs → + New workflow**, open Ask OE and type *\"create a weekly Monday 9am competitor watch where the CMO checks our top three competitors for pricing and product changes, and send it to me\"*. The name, steps and schedule fill in; you review them and click **Create workflow**.\n\n**Good to know:** panel conversations are normal chat sessions — they appear in your session history and the audit log like any other turn.",
+ "markdown": "**What it is:** A page-aware assistant panel docked on the right of every screen (except the chat home, which *is* the chat). Open it with the **Ask OE** button in the top bar or **Ctrl/Cmd + .** — it's the same Executive you talk to in chat, but it knows what page you're looking at.\n\n**What it does:**\n\n- **Explains the current page.** Ask \"what does this page do?\" or \"what does authority scope mean?\" and the answer is grounded in this guide's section for the page you're on.\n- **Fills forms for you.** On a screen with a form (the workflow builder, the Add-person dialog, the company profile), describe what you want in plain language and the suggested values land directly in the form, highlighted so you can see what came from the Executive.\n- **You always click Save.** Ask OE never submits a form. Suggested values are just that — review them, edit anything, and save through the form's normal button. An **Undo** on the proposal card restores what was there before, and a highlight clears the moment you edit that field yourself.\n\n**How to use:**\n\n1. On any page, click **Ask OE** in the top bar or press **Ctrl/Cmd + .** (press it again to close).\n2. Ask about the page — \"what's the difference between Flag and Reject here?\" — or, on a form page, describe what you want filled in.\n3. Check the highlighted fields. Edit anything that's off, then click the form's own **Save** / **Create** button. Click **Undo** on the proposal card to put the form back as it was.\n4. Click **New conversation** in the panel header to start fresh.\n\n**Where it works:** every page inside the app shell. Form-filling is wired into the workflow builder (**Workflows → + New workflow**), the **Add person** dialog, and the **Company profile**; other pages get the explain tier, with form support arriving screen by screen.\n\n**Example:** on **Workflows → + New workflow**, open Ask OE and type *\"create a weekly Monday 9am competitor watch where the CMO checks our top three competitors for pricing and product changes, and send it to me\"*. The name, steps and schedule fill in; you review them and click **Create workflow**.\n\n**Good to know:** panel conversations are normal chat sessions — they appear in your session history and the audit log like any other turn.",
"mermaid": null,
"generated_at": "2026-09-23T00:00:00+00:00"
}
diff --git a/packages/core/openexecutive/guide/prebuilt/jobs.json b/packages/core/openexecutive/guide/prebuilt/jobs.json
index 84ee6b82..6a4cf75d 100644
--- a/packages/core/openexecutive/guide/prebuilt/jobs.json
+++ b/packages/core/openexecutive/guide/prebuilt/jobs.json
@@ -1,7 +1,7 @@
{
"section_id": "jobs",
- "title": "Jobs (Workflows)",
- "markdown": "**What it is:** Structured, multi-step workflows that produce a *deliverable* — a board deck, a go-to-market plan, a performance review — rather than just a chat reply.\n\n**What it does:**\n\n- Browse the workflow catalog as compact cards; filter by area with the chips at the top (**Custom** holds yours, **System** holds the jobs Open Executive runs on its own, like the morning brief).\n- Start a run and watch it stream its progress step by step.\n- See your runs split into **Active**, **Awaiting sign-off**, **Done**, and **Error**, and search them by name.\n- Create your own **custom workflow** by describing it: the assistant asks a few clarifying questions, then drafts it for you to review.\n- Put a custom workflow on a **schedule** (e.g. every Monday at 09:00) so it runs without being asked.\n- Each finished run produces a document you can read and keep.\n\n**How to use:**\n\n*Run a workflow*\n\n1. Open **Jobs** and click a workflow in the **Catalog** — narrow the list with the chips or the search box.\n2. Fill in the fields (required ones have a red \\*). **Insert example** or **Load sample run** fills in realistic values if you just want to try it.\n3. Click **Continue**, then **Run job**. Progress streams step by step; when it finishes you land on the run page, with **Copy** and **Download .md**.\n\n*Build your own*\n\n1. Click **+ New workflow** and describe the job in plain words — what it should produce, who it's for, and how often — or pick one of the starter suggestions.\n2. Answer the clarifying questions (usually two or three) by typing or by clicking a suggested answer. **Draft it now** skips the rest.\n3. Review the draft: its steps, schedule, what you fill in each run, and the assumptions it made.\n4. Click **Create workflow**, or **Keep refining** and type what to change, or **Edit details** to fine-tune it field by field. It appears under **Custom** in the Catalog, with **Edit** and **Delete**.\n\n*Advanced editor* — reached from **Edit** on a custom workflow, **Edit details** on a draft, or **Use the advanced editor**:\n\n1. **Details:** a unique **Name** in snake_case (e.g. `weekly_competitor_watch`; 3–49 characters, starting with a letter), a title, description, section and estimated minutes.\n2. **Input fields:** click **+ Add field** for anything the person running it must supply. Use a field in a step's goal as `{field_name}`.\n3. **Steps:** add **+ Specialist** steps (pick a specialist, write its goal) and, if someone must sign off, an **+ Approval gate** (who to ask, the question, a timeout, and what happens on timeout). New steps are added at the bottom — use **↑** to move them above the synthesis step, which pulls everything together and must stay last; put an approval gate just before it. Up to 12 steps and 16 input fields.\n4. **Schedule (optional):** tick **Run on a schedule**, enter a cadence, and choose who the result is delivered to. Scheduled workflows can't have required inputs or approval gates.\n5. Click **Create workflow** (**Save changes** when editing).\n\nCadences are written like this (times are UTC): `daily@09:00`, `weekly@mon@09:00`, or `quarterly@01-09:00` (the 1st of January, April, July and October).\n\n*Signing off a paused run* — when a run reaches an approval gate it moves to **Awaiting sign-off** and the approver is messaged directly. They answer by replying on Slack, Discord or Telegram — \"yes\", \"LGTM\", \"no\", \"not now\". There's no approve button in the web app. \"No\" or \"not now\" ends the run.\n\n**From chat:**\n\n- *\"What workflows can you run?\"* or *\"Run a competitive teardown of Acme.\"* — the Executive runs it and brings the result back into the conversation.\n- *\"Build me a workflow called weekly_competitor_watch: the CMO checks our top three competitors for pricing and product changes, then summarise. Run it every Monday at 09:00 UTC and send it to me.\"* — the Executive drafts it, shows you a summary, and saves it once you say yes.\n\n*Note: outputs are listed in Artifacts. Ask OE can also fill in the advanced editor form for you.*",
+ "title": "Workflows",
+ "markdown": "**What it is:** Structured, multi-step workflows that produce a *deliverable* — a board deck, a go-to-market plan, a performance review — rather than just a chat reply.\n\n**What it does:**\n\n- Browse the workflow catalog as compact cards; filter by area with the chips at the top (**Custom** holds yours, **System** holds the workflows Open Executive runs on its own, like the morning brief).\n- Start a run and watch it stream its progress step by step.\n- See your runs split into **Active**, **Awaiting sign-off**, **Done**, and **Error**, and search them by name.\n- Create your own **custom workflow** by describing it: the assistant asks a few clarifying questions, then drafts it for you to review.\n- Put a custom workflow on a **schedule** (e.g. every Monday at 09:00) so it runs without being asked.\n- Each finished run produces a document you can read and keep.\n\n**How to use:**\n\n*Run a workflow*\n\n1. Open **Workflows** and click a workflow in the **Catalog** — narrow the list with the chips or the search box.\n2. Fill in the fields (required ones have a red \\*). **Insert example** or **Load sample run** fills in realistic values if you just want to try it.\n3. Click **Continue**, then **Run workflow**. Progress streams step by step; when it finishes you land on the run page, with **Copy** and **Download .md**.\n\n*Build your own*\n\n1. Click **+ New workflow** and describe the job in plain words — what it should produce, who it's for, and how often — or pick one of the starter suggestions.\n2. Answer the clarifying questions (usually two or three) by typing or by clicking a suggested answer. **Draft it now** skips the rest.\n3. Review the draft: its steps, schedule, what you fill in each run, and the assumptions it made.\n4. Click **Create workflow**, or **Keep refining** and type what to change, or **Edit details** to fine-tune it field by field. It appears under **Custom** in the Catalog, with **Edit** and **Delete**.\n\n*Advanced editor* — reached from **Edit** on a custom workflow, **Edit details** on a draft, or **Use the advanced editor**:\n\n1. **Details:** a unique **Name** in snake_case (e.g. `weekly_competitor_watch`; 3–49 characters, starting with a letter), a title, description, section and estimated minutes.\n2. **Input fields:** click **+ Add field** for anything the person running it must supply. Use a field in a step's goal as `{field_name}`.\n3. **Steps:** add **+ Specialist** steps (pick a specialist, write its goal) and, if someone must sign off, an **+ Approval gate** (who to ask, the question, a timeout, and what happens on timeout). New steps are added at the bottom — use **↑** to move them above the synthesis step, which pulls everything together and must stay last; put an approval gate just before it. Up to 12 steps and 16 input fields.\n4. **Schedule (optional):** tick **Run on a schedule**, enter a cadence, and choose who the result is delivered to. Scheduled workflows can't have required inputs or approval gates.\n5. Click **Create workflow** (**Save changes** when editing).\n\nCadences are written like this (times are UTC): `daily@09:00`, `weekly@mon@09:00`, or `quarterly@01-09:00` (the 1st of January, April, July and October).\n\n*Signing off a paused run* — when a run reaches an approval gate it moves to **Awaiting sign-off** and the approver is messaged directly. They answer by replying on Slack, Discord or Telegram — \"yes\", \"LGTM\", \"no\", \"not now\". There's no approve button in the web app. \"No\" or \"not now\" ends the run.\n\n**From chat:**\n\n- *\"What workflows can you run?\"* or *\"Run a competitive teardown of Acme.\"* — the Executive runs it and brings the result back into the conversation.\n- *\"Build me a workflow called weekly_competitor_watch: the CMO checks our top three competitors for pricing and product changes, then summarise. Run it every Monday at 09:00 UTC and send it to me.\"* — the Executive drafts it, shows you a summary, and saves it once you say yes.\n\n*Note: outputs are listed in Artifacts. Ask OE can also fill in the advanced editor form for you.*",
"mermaid": null,
"generated_at": "2026-09-23T00:00:00+00:00"
}
diff --git a/packages/core/openexecutive/guide/sections.py b/packages/core/openexecutive/guide/sections.py
index ccb86366..fb44e317 100644
--- a/packages/core/openexecutive/guide/sections.py
+++ b/packages/core/openexecutive/guide/sections.py
@@ -52,7 +52,7 @@ GUIDE_SECTIONS: list[GuideSection] = [
),
GuideSection(
id="jobs",
- title="Jobs (Workflows)",
+ title="Workflows",
sub="Multi-step workflows that produce a deliverable — board prep, GTM plan, perf review.",
),
GuideSection(
diff --git a/packages/core/openexecutive/workflows/gate.py b/packages/core/openexecutive/workflows/gate.py
index 20fb6405..07f32382 100644
--- a/packages/core/openexecutive/workflows/gate.py
+++ b/packages/core/openexecutive/workflows/gate.py
@@ -157,7 +157,7 @@ def ensure_workflow_event(event: object, *, site: str) -> WorkflowEvent:
raise UnsupportedGateError(
f"{site}: workflow yielded an approval gate, but this runner "
"cannot pause for a human — every step after the gate would be "
- "dropped. Run this workflow from the /jobs page or the chat tool."
+ "dropped. Run this workflow from the Workflows page (/jobs) or the chat tool."
)
return cast(WorkflowEvent, event)
diff --git a/packages/ui/src/app/guide/page.tsx b/packages/ui/src/app/guide/page.tsx
index 8ce25f96..52d45d27 100644
--- a/packages/ui/src/app/guide/page.tsx
+++ b/packages/ui/src/app/guide/page.tsx
@@ -13,7 +13,7 @@ const SECTIONS = [
{ id: 'today', label: 'Today / Morning Brief', sub: 'What needs you right now: proposals, department health, and people with open items.' },
{ id: 'pulse', label: 'Pulse (Memory)', sub: "The Executive's running memory — decisions made, initiatives in flight, advice gathered." },
{ id: 'review', label: 'Review Queue', sub: 'Built-in knowledge is trusted by default. Review what you upload or edit, or send a domain for review yourself.' },
- { id: 'jobs', label: 'Jobs (Workflows)', sub: 'Multi-step workflows that produce a deliverable — board prep, GTM plan, perf review.' },
+ { id: 'jobs', label: 'Workflows', sub: 'Multi-step workflows that produce a deliverable — board prep, GTM plan, perf review.' },
{ id: 'artifacts', label: 'Artifacts', sub: 'Your library of finished documents — drafts and workflow outputs in one place.' },
{ id: 'watchlist', label: 'Watch List', sub: 'External monitors — stock tickers, RSS feeds, status pages, web queries — that raise alerts.' },
{ id: 'departments', label: 'Departments', sub: 'Org units, each with goals, an authority level, and a specialist behind it.' },
diff --git a/packages/ui/src/app/jobs/[name]/page.tsx b/packages/ui/src/app/jobs/[name]/page.tsx
index 696f3ad4..0e7b0a8f 100644
--- a/packages/ui/src/app/jobs/[name]/page.tsx
+++ b/packages/ui/src/app/jobs/[name]/page.tsx
@@ -190,7 +190,7 @@ export default function JobDetailPage() {
<div className="flex flex-col h-full bg-surface text-fg items-center justify-center">
<div className="text-sm text-red-400 mb-4">Error: {loadError}</div>
<Link href="/jobs" className="text-sm text-fg-muted hover:text-fg">
- ← Back to jobs
+ ← Back to workflows
</Link>
</div>
);
diff --git a/packages/ui/src/app/jobs/new/page.tsx b/packages/ui/src/app/jobs/new/page.tsx
index e7be5b6b..6e581e4d 100644
--- a/packages/ui/src/app/jobs/new/page.tsx
+++ b/packages/ui/src/app/jobs/new/page.tsx
@@ -199,7 +199,7 @@ function BuilderInner() {
formId: "workflow_builder",
title: editName ? "Edit workflow" : "New workflow",
description:
- "Builds a reusable executive job from specialist steps, optional approval gates, and a final synthesis step.",
+ "Builds a reusable workflow from specialist steps, optional approval gates, and a final synthesis step.",
getFields: (): PageFormField[] => [
{
name: "name",
@@ -855,13 +855,13 @@ function AdvancedBuilderPage() {
<div className="max-w-3xl mx-auto">
<div className="mb-6">
<Link href="/jobs" className="text-xs text-fg-muted hover:text-fg">
- ← Back to jobs
+ ← Back to workflows
</Link>
<h1 className="text-2xl font-semibold text-fg mt-2 mb-1">
{editing ? "Edit workflow" : "New workflow"}
</h1>
<p className="text-sm text-fg-muted">
- Build a reusable executive job from specialist steps, optional
+ Build a reusable workflow from specialist steps, optional
approval gates, and a final synthesis step.
{!editing && (
<>
@@ -887,7 +887,7 @@ function WizardPage() {
<div className="border-b border-line px-6 py-4">
<div className="max-w-3xl mx-auto">
<Link href="/jobs" className="text-xs text-fg-muted hover:text-fg">
- ← Back to jobs
+ ← Back to workflows
</Link>
<h1 className="text-xl font-semibold text-fg mt-1">New workflow</h1>
</div>
diff --git a/packages/ui/src/app/jobs/page.tsx b/packages/ui/src/app/jobs/page.tsx
index 34136915..9dfefd29 100644
--- a/packages/ui/src/app/jobs/page.tsx
+++ b/packages/ui/src/app/jobs/page.tsx
@@ -240,7 +240,7 @@ function JobsPageInner() {
</div>
{loading && (
- <div className="text-sm text-fg-muted">Loading jobs…</div>
+ <div className="text-sm text-fg-muted">Loading workflows…</div>
)}
{error && (
<div className="text-sm text-red-400 mb-4">Error: {error}</div>
@@ -424,7 +424,7 @@ function CatalogView({
<SearchInput
value={query}
onChange={onQueryChange}
- placeholder="Search jobs…"
+ placeholder="Search workflows…"
/>
</div>
<div className="mb-4 flex flex-wrap gap-1.5">
@@ -446,10 +446,10 @@ function CatalogView({
</div>
{workflows.length === 0 ? (
- <div className="text-sm text-fg-muted">No jobs registered yet.</div>
+ <div className="text-sm text-fg-muted">No workflows yet.</div>
) : visible.length === 0 ? (
<div className="text-sm text-fg-muted">
- {query ? <>No jobs match &ldquo;{query}&rdquo;.</> : "Nothing here yet."}
+ {query ? <>No workflows match &ldquo;{query}&rdquo;.</> : "Nothing here yet."}
</div>
) : section === "all" ? (
<div className="space-y-5">
@@ -680,9 +680,9 @@ export default function JobsPage() {
<div className="max-w-6xl mx-auto">
<div className="mb-4 flex items-start justify-between gap-4">
<div className="min-w-0">
- <h1 className="text-xl font-semibold text-fg">Executive Jobs</h1>
+ <h1 className="text-xl font-semibold text-fg">Workflows</h1>
<p className="text-sm text-fg-muted">
- Multi-step jobs that produce a finished deliverable.
+ Multi-step workflows that produce a finished deliverable.
</p>
</div>
<Link
diff --git a/packages/ui/src/app/jobs/runs/[id]/page.tsx b/packages/ui/src/app/jobs/runs/[id]/page.tsx
index 6ddabb17..b6963010 100644
--- a/packages/ui/src/app/jobs/runs/[id]/page.tsx
+++ b/packages/ui/src/app/jobs/runs/[id]/page.tsx
@@ -121,7 +121,7 @@ export default function RunDetailPage() {
<div className="flex flex-col h-full bg-surface text-fg items-center justify-center">
<div className="text-sm text-red-400 mb-4">Error: {error}</div>
<Link href="/jobs" className="text-sm text-fg-muted hover:text-fg">
- ← Back to jobs
+ ← Back to workflows
</Link>
</div>
);
diff --git a/packages/ui/src/components/WorkflowRunner.tsx b/packages/ui/src/components/WorkflowRunner.tsx
index 8c8c8d19..8a7b1a0c 100644
--- a/packages/ui/src/components/WorkflowRunner.tsx
+++ b/packages/ui/src/components/WorkflowRunner.tsx
@@ -116,7 +116,7 @@ export default function WorkflowRunner({
onClick={handleStart}
className="px-4 py-2 rounded-md bg-indigo-600 hover:bg-indigo-500 text-white text-sm font-medium transition"
>
- Run job
+ Run workflow
</button>
<button
type="button"
diff --git a/packages/ui/src/components/askoe/AskOEContext.tsx b/packages/ui/src/components/askoe/AskOEContext.tsx
index bfe33086..bb910311 100644
--- a/packages/ui/src/components/askoe/AskOEContext.tsx
+++ b/packages/ui/src/components/askoe/AskOEContext.tsx
@@ -55,7 +55,7 @@ const ROUTE_GUIDE_MAP: Array<{ prefix: string; guideId: string; title: string }>
{ prefix: "/today", guideId: "today", title: "Today" },
{ prefix: "/memories", guideId: "pulse", title: "Pulse" },
{ prefix: "/review", guideId: "review", title: "Review queue" },
- { prefix: "/jobs", guideId: "jobs", title: "Jobs" },
+ { prefix: "/jobs", guideId: "jobs", title: "Workflows" },
{ prefix: "/artifacts", guideId: "artifacts", title: "Artifacts" },
{ prefix: "/watchlist", guideId: "watchlist", title: "Watch list" },
{ prefix: "/departments", guideId: "departments", title: "Departments" },
diff --git a/packages/ui/src/components/shell/AppShell.tsx b/packages/ui/src/components/shell/AppShell.tsx
index 36c8152f..100a28ad 100644
--- a/packages/ui/src/components/shell/AppShell.tsx
+++ b/packages/ui/src/components/shell/AppShell.tsx
@@ -42,7 +42,7 @@ const SEGMENT_LABELS: Record<string, string> = {
skills: "Skills",
memories: "Pulse",
knowledge: "Knowledge base",
- jobs: "Jobs",
+ jobs: "Workflows",
artifacts: "Artifacts",
runs: "Runs",
new: "New",
diff --git a/packages/ui/src/components/shell/navConfig.ts b/packages/ui/src/components/shell/navConfig.ts
index 321ad92d..0dc12d76 100644
--- a/packages/ui/src/components/shell/navConfig.ts
+++ b/packages/ui/src/components/shell/navConfig.ts
@@ -56,7 +56,7 @@ export function buildPrimaryNav({ isOnboarded = true, reviewBadge = 0 }: BuildOp
},
{
href: "/jobs",
- label: "Jobs",
+ label: "Workflows",
icon: "doc",
description:
"Multi-step workflows that produce a deliverable — board prep, GTM plans, reviews.",
@@ -226,7 +226,7 @@ export const MOBILE_PRIMARY: NavItem[] = [
},
{
href: "/jobs",
- label: "Jobs",
+ label: "Workflows",
icon: "doc",
description:
"Multi-step workflows that produce a deliverable — board prep, GTM plans, reviews.",