Skip to content

Workbench

Preview one task change, or compose prompts and jobs your team can review.

This unreleased build supports one manual task date change through Noc with explicit confirmation and receipts. Prompts, jobs and workflows remain reviewable records; a confirmed saved-prompt job reaches an unavailable outcome because no executor is configured.

What Workbench is

In a permitted Tenant-wide context, enter a full task UUID and date or choose from at most 50 of your due tasks. Preview the stored dates, then explicitly Change due date. Reload never executes automatically; conditional Undo links its reversal receipt.

A prompt is written once and can be archived and restored later without losing its history.

A job queues a prompt to run, but this build has no executor: a confirmed job always reaches an honest, unavailable outcome rather than a simulated answer.

A workflow composes several prompts and jobs into one reviewable record, kept separately from any single run.

Work it supports today

Each of these starts on a real page in the product. Nothing here is planned or promised.

  • Write a prompt and see what running it would do

    A queued job that reaches its outcome honestly — unavailable, since no model provider exists.

    1. Open Prompts and choose New prompt.
    2. Write it and save it.
    3. Queue a job from it.
    4. Read the job's outcome.
  • Cancel a job you no longer need

    A queued or unavailable job cancelled, with the reason recorded on it.

    1. Open Jobs.
    2. Find one that is queued or unavailable.
    3. Cancel it.
  • Archive a prompt you've retired

    A prompt out of your active list, restorable later if you need it again.

    1. Open Prompts.
    2. Open the one you're done with.
    3. Archive it.
    4. Restore it later if you need it.
  • Compose a workflow from several prompts

    One reviewable record naming the prompts a workflow should run, in order.

    1. Open Workflows and choose New workflow.
    2. Add the prompts it should run, in order.
    3. Save it as one record.

By hand: queue a job and read its honest outcome

Priya Anand at Halden Rowe Joinery wants to try a prompt that drafts a follow-up email, without a model provider connected.

  1. Priya opens Workbench, then Prompts, and writes the draft prompt.
  2. She opens Jobs and queues a job from it.
  3. The job reaches its outcome: unavailable, because no model provider is configured in this build.
  4. Nothing is invented in its place; the honest outcome is the record she keeps.

Fictional names. Start here: /workbench/prompts

Or let Noc do it

Noc plans the steps, previews every effect, asks before anything irreversible, and hands back one receipt. Autopilot is off by default.

“Noc, cancel the job that's been stuck waiting on a provider, and archive the prompt behind it — I'm done with it.”

  1. Read the job's current state. Nothing is written.
  2. Cancel the job. This is not undone, so Noc asks first.
  3. Archive the prompt behind it. Archiving can be undone by restoring it.
Before anything irreversible
Before it cancels the job or archives the prompt, Noc previews the exact effect and asks for your confirmation first.
What you get back
One receipt for each step that ran, and one for the whole request, so you can see exactly what happened.

Capabilities this plan can use: 3. Each is registered, permission-bound and previewed.

What stays in your hands

  • Your permissions decide, every time

    Existing authoring keeps workbench.read/write and saved jobs keep workbench.run. The manual task operation separately requires workbench.read, noc.read, noc.use, tasks.read, tasks.write and companies.read in a tenant-wide context. Noc carries your permissions and never more.

  • A confirmed job never invents an answer

    Every provider seam in this build answers unavailable; a run records that refusal instead of a fabricated result.

  • Cancelling is deliberate, and it asks first

    Cancelling a job is not undone, so Noc always previews it and waits for your confirmation before it runs.

The honest states

What the product really shows when there is nothing yet, when it refuses, and where this build stops.

  • What you see first

    A new workspace has no prompts yet

    Prompts shows nothing until the first one is written; there is no sample prompt or job.

  • When something is refused

    Cancelling a job that already finished is refused

    A job that is no longer queued or unavailable cannot be cancelled; the action is refused outright, not silently ignored.

  • Not available in this build

    No prompt runs against a model provider

    Every provider seam in this build answers unavailable; a confirmed job records that refusal instead of inventing an answer.

Next

To see Workbench you need a membership in a workspace. Acting needs the permissions your administrator grants.