taskchef 8.7.1 → 9.0.1

package/src/{dashboard/react → ui}/components/TaskCard.tsx

@@ -1,6 +1,6 @@
 import { Box, Paper, Stack, Text, Title } from "@mantine/core";
 import { IconArrowUpRight } from "@tabler/icons-react";
-import { latestTurnPresentation } from "../../state.js";
+import { latestTurnPresentation } from "../state.js";
 import type { Task } from "../types";
 import { GitHubLinks } from "./GitHubLinks";
 import { LinkedText } from "./LinkedText";

package/src/{dashboard/react → ui}/components/TurnContent.tsx

@@ -3,7 +3,7 @@ import { useCallback, useLayoutEffect, useRef, useState } from "react";
 import type { Task } from "../types";
 import { ImageGallery } from "./ImageGallery";
 import { ReplyImagePreview } from "./ReplyImagePreview";
-import { formatWorkedDuration } from "../../time.js";
+import { formatWorkedDuration } from "../time.js";
 import { ReplyMarkdown } from "./ReplyMarkdown";
 
 const hidePromptImage = () => null;

package/src/{dashboard/react → ui}/presentation.ts

@@ -3,7 +3,7 @@ import {
   durationBetween,
   reportedWorkSummary,
   terminalTurnDuration,
-} from "../../reported-work.js";
+} from "../reported-work.js";
 
 export { durationBetween };
 

package/src/user-prompt.js

@@ -3,6 +3,17 @@ import { normalizeUri } from "micromark-util-sanitize-uri";
 // Convert Codex's supplied prompt context to readable Markdown. Unknown or
 // malformed context stays visible; this does not change the recorded input.
 export function displayUserPrompt(text) {
+  const questionReply = /^\s*<send_user_message_question_reply>([\s\S]*)<\/send_user_message_question_reply>\s*$/.exec(text);
+  if (questionReply) {
+    try {
+      const value = JSON.parse(questionReply[1]);
+      const replies = Array.isArray(value) ? value : [value];
+      if (replies.length && replies.every(reply => reply && typeof reply.question === "string" && typeof reply.answer === "string")) {
+        return replies.map(reply => `${reply.question.split('\n').map(line => `> ${line}`).join('\n')}\n\n${reply.answer}`).join('\n\n');
+      }
+    } catch { /* Preserve unrecognized input rather than losing the user's prompt. */ }
+    return text;
+  }
   const requestHeading = /^##? My request:[ \t]*(?:\r?\n|$)/m.exec(text);
   if (!requestHeading || !/^(?:[ \t]*\r?\n)*(?:# Response annotations:|# Files mentioned by the user:|<in-app-browser-context source="ambient-ui-state">)\r?\n/.test(text)) return text;
   const context = text.slice(0, requestHeading.index);

package/src/version.js

@@ -6,4 +6,3 @@ const packageMetadata = require("../package.json");
 export const TASKCHEF_APP_NAME = require("../.codex-plugin/plugin.json").interface.displayName;
 
 export const TASKCHEF_VERSION = packageMetadata.version;
-export const DASHBOARD_SERVER_VERSION = "4";

package/BACKLOG.md

@@ -1,48 +0,0 @@
-# TaskChef backlog
-
-[`docs/spec.md`](docs/spec.md) is the current contract. These ideas need a concrete user case and a
-clear data model before implementation.
-
-## Task history views
-
-- Add date ranges and title search if the task log becomes difficult to
-  browse.
-- Consider export formats for personal activity reports.
-- Define archival or retention only when real logs become large enough to need
-  it.
-- Consider grouping entries created from one broad request without storing the
-  full original prompt.
-
-## Optional reports
-
-- Consider user-scheduled, read-only digests that query recorded Codex tasks
-  and publish a report without writing status or results to the TaskChef
-  workspace.
-- Define batching and partial-read behavior for large task histories.
-- Decide whether inaccessible or deleted Codex tasks need a separate report
-  category.
-
-## Remote projects
-
-- Import remote connection projects returned by native project discovery.
-- Persist the native project and host identity needed to distinguish identical
-  paths on different hosts.
-- Re-resolve remote identities before dispatch.
-- Define unavailable-host, renamed-project, moved-path, and stale-identity
-  behavior.
-- Evaluate isolated worktrees and conflict handling for concurrent tasks in one
-  project.
-
-## Integrations
-
-- Add GitHub automation only when task history alone is insufficient.
-- Evaluate automatic project discovery rules and exclusions.
-- Consider multiple executor threads for one logical assignment if a real
-  workflow requires it.
-
-## Transport-authenticated executor identity
-
-- If custom MCP later receives authenticated calling-task metadata, compare it
-  with the executor's `link_task` assertion.
-- Keep the current local cooperative trust model until such metadata exists;
-  do not reintroduce parent/session identity, hooks, task search, or polling.

package/assets/e2e-benchmark-example.json

@@ -1,50 +0,0 @@
-{
-  "schemaVersion": 2,
-  "benchmark": "taskchef-executor-self-link-e2e",
-  "taskchefVersion": "0.0.0",
-  "runId": "replace-with-run-id",
-  "startedAt": "2026-08-24T10:00:00.000Z",
-  "completedAt": "2026-08-24T10:01:00.000Z",
-  "workload": {
-    "project": "example-project",
-    "title": "Provisional self-link example",
-    "prompt": "Pause for approval, then complete the requested work."
-  },
-  "task": {
-    "taskId": "00000000-0000-4000-8000-000000000000",
-    "threadId": "00000000-0000-7000-8000-000000000000",
-    "clientThreadId": "local:replace-with-provisional-id",
-    "recorded": true,
-    "linked": true
-  },
-  "turns": {
-    "needsInput": "00000000-0001-7000-8000-000000000000",
-    "completion": "00000000-0002-7000-8000-000000000000"
-  },
-  "events": {
-    "preparedAt": "2026-08-24T10:00:00.000Z",
-    "recordedAt": "2026-08-24T10:00:01.000Z",
-    "createdAt": "2026-08-24T10:00:02.000Z",
-    "linkedAt": "2026-08-24T10:00:05.000Z",
-    "needsInputAt": "2026-08-24T10:00:20.000Z",
-    "followedUpAt": "2026-08-24T10:00:40.000Z",
-    "completedAt": "2026-08-24T10:01:00.000Z"
-  },
-  "validation": {
-    "exactMarkerCorrelated": true,
-    "noDispatcherPostCreateReads": true,
-    "childIdentityVerified": true,
-    "parentIdentityRejected": true,
-    "linkRetryVerified": true,
-    "needsInputVerified": true,
-    "followUpTurnFresh": true,
-    "dashboardDeepLinkVerified": true,
-    "outputVerified": true
-  },
-  "summary": {
-    "totalWallMs": 60000,
-    "provisionalPath": true,
-    "linked": true,
-    "freshFollowUp": true
-  }
-}

package/assets/taskchef-dispatcher-instructions.md

@@ -1,44 +0,0 @@
-<!-- taskchef:dispatcher-instructions:start -->
-# TaskChef Dispatcher Instructions
-
-This folder is the canonical per-user TaskChef dispatcher workspace.
-
-- Early in every dispatcher turn, best-effort call the TaskChef
-  `ensure_dashboard` MCP tool. Dashboard startup failure must not block direct
-  TaskChef answers, reporting, or delegation.
-- A request to start, recover, or open the TaskChef dashboard is TaskChef
-  maintenance, not delegated project work. Use `$taskchef-dashboard`.
-- Use `$taskchef-bootstrap` when initializing or refreshing this workspace,
-  changing or listing its configured projects, running TaskChef doctor,
-  or repairing its managed instructions.
-- When the user asks to answer, follow up, resume, or continue the same
-  recorded assignment in its existing executor task, use `$taskchef-copilot`
-  before the general delegation rule. A direct imperative that names the exact
-  existing task is explicit send authorization, but copilot must immediately
-  re-read that exact task and apply its state and identity guardrails.
-- For every other actionable request that asks for an independent new outcome,
-  use `$taskchef-delegate` automatically, even when the user does not explicitly
-  say "delegate" or mention TaskChef.
-- Delegation lists native projects once per batch, reconciles that exact
-  snapshot once, and routes only to one eligible exact native target.
-- GitHub issue and pull-request URLs may identify any repository advertised by
-  a configured project, including child repositories of managed workspaces.
-- Do not perform delegated work directly in the dispatcher thread.
-- Return immediately after dispatch, as required by `$taskchef-delegate`.
-- Answer directly only when the user explicitly asks about TaskChef itself or
-  explicitly says not to delegate.
-- Use `$taskchef-copilot` when the user asks what delegated work finished,
-  what needs attention, why it failed or needs input, or what should happen
-  next, including same-assignment continuation in an exact existing executor.
-  Copilot uses the cached TaskChef brief by default; the dashboard is the
-  primary monitoring and browsing UI. Live verification is explicit or
-  contradiction-driven, focused, and never polled.
-- Explicit invocations of TaskChef skills from other Codex projects use this
-  same workspace and task history through TaskChef's global resolution rules.
-- Every final response in this dispatcher workspace must end with this exact
-  clickable link on its final non-empty line:
-  `[TaskChef Dashboard](http://127.0.0.1:3210/)`. Keep any
-  `::created-thread{...}` directive required by delegation on its own line
-  immediately before the dashboard link so the immediate-return contract still
-  holds. Include the link even when `ensure_dashboard` failed.
-<!-- taskchef:dispatcher-instructions:end -->

package/bin/taskchef.js

@@ -1,20 +0,0 @@
-#!/usr/bin/env node
-
-import { runCli } from "../src/cli.js";
-
-try {
-  process.exitCode = await runCli(process.argv.slice(2));
-} catch (error) {
-  if (process.argv.includes("--json")) {
-    process.stdout.write(`${JSON.stringify({
-      error: {
-        code: error.code ?? "ERROR",
-        message: error.message,
-        ...(error.details ? { details: error.details } : {}),
-      },
-    })}\n`);
-  } else {
-    process.stderr.write(`taskchef: ${error.message}\n`);
-  }
-  process.exitCode = 1;
-}