Skip to content

docs(tasks): nullable title on task runs — originating scheduled task's title#268

Open
sweetmantech wants to merge 1 commit into
mainfrom
docs/task-runs-title
Open

docs(tasks): nullable title on task runs — originating scheduled task's title#268
sweetmantech wants to merge 1 commit into
mainfrom
docs/task-runs-title

Conversation

@sweetmantech

@sweetmantech sweetmantech commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

What

Amends the TaskRunResponse schema in api-reference/openapi/releases.json with a new nullable title field: the originating scheduled task's title, when resolvable. Purely additive (+5 lines, JSON parse re-validated, all pre-existing bytes untouched).

Why

GET /api/tasks/runs proxies Trigger.dev runs, which only carry taskIdentifier — and every scheduled prompt shares customer-prompt-task, so the chat homepage renders five identical "Scheduled Task" rows (recoupable/chat#1850, video-parity item 1). The api resolves each list-mode run's title by joining Trigger's filter[schedule] runs against the account's scheduled_actions (title + trigger_schedule_id). title is null when a run cannot be mapped to a scheduled task (e.g. non-scheduled runs), and is not present in retrieve mode (runId provided) — mirroring the schema's existing mode-scoped field notes.

Links

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features
    • Task run responses now include an optional title field when available, helping identify the originating scheduled task in run listings.
    • If a scheduled task can’t be resolved, the field may be returned as null.

Summary by cubic

Adds a nullable title field to TaskRunResponse so run listings can show the originating scheduled task’s title. Improves readability of GET /api/tasks/runs by naming scheduled runs; the field is only in list mode, may be null if unresolved, and is omitted in retrieve mode.

Written for commit 83faa16. Summary will update on new commits.

Review in cubic

…uled task)

GET /api/tasks/runs list mode gains a per-run title resolved from the
originating scheduled_actions row (via its trigger_schedule_id). Null when
the run cannot be mapped to a scheduled task; not present in retrieve mode.

Contract for recoupable/chat#1850 (video-parity: named homepage run rows).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@cursor

cursor Bot commented Jul 7, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f1f01293-4c8a-4a62-9e49-8d4e39596f54

📥 Commits

Reviewing files that changed from the base of the PR and between a902d8e and 83faa16.

📒 Files selected for processing (1)
  • api-reference/openapi/releases.json

📝 Walkthrough

Walkthrough

The OpenAPI specification for TaskRunResponse is updated to include a new optional, nullable title field representing the originating scheduled task's title, applicable only when listing runs without a specified runId.

Changes

TaskRunResponse Schema Update

Layer / File(s) Summary
Add title field to schema
api-reference/openapi/releases.json
Adds a nullable title string property to TaskRunResponse, documented as populated only during run listing and null otherwise.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Estimated code review effort

(see above)

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly reflects the main change: adding a nullable task-run title derived from the originating scheduled task.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/task-runs-title

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant