Skip to content

Orchestrator status read and status posts #440

Closed

Description

@tannerpolley

From #425 item 1 (P1). Owner chose this on 2026-11-17.

Problem

To answer "where are we on everything?", the orchestrator has to stitch together several t3_thread_list, t3_thread_read and task_status calls. It also has no rule to tell the owner when a child finishes, blocks or fails.

Proposal

  1. One cheap read, either an extension of get_repository_orchestration or a new tool, that returns the root's children grouped as working, needs you (pending question or approval, or a failed run) and ready for review (open PR, no agent working). Each child shows its issue, PR link, last summary and elapsed time.
  2. A short line in the Orchestrator instructions: answer status questions from that read, and post one line when a child finishes, blocks or fails. First check whether orchestrationInstructions.ts already says this.

Constraints

Done when

  • One tool call returns the grouped status.
  • The instruction is present, and its eval or context-budget check passes.
  • There are focused tests for the grouping.

Blocked by #418.

Activity

  1. tannerpolley commented on Nov 18, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code status: Done

    Issue: #440 Orchestrator status read and status posts

    Thread: thread:delegated-task:command%3Amcp%3Aaf93ca41-fec6-470a-96c2-8aadf4aef446%3Adelegate-task%3Adelegate-440-2026-11-18

    Model: gpt-6.2-sol

    Branch: issue-440-repository-child-status

    Updated: 2026-11-18T21:02:13.717Z

  2. tannerpolley commented on Nov 18, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code closeout: done

    Issue: #440 Orchestrator status read and status posts
    Thread: thread:delegated-task:command%3Amcp%3Aaf93ca41-fec6-470a-96c2-8aadf4aef446%3Adelegate-task%3Adelegate-440-2026-11-18
    Model: gpt-6.2-sol
    Branch: issue-440-orchestrator-status-read-and-status
    Completed: 2026-11-18T20:40:00.470Z

    Implemented #440 in draft PR #482. One repository_status call groups the root’s active direct children as Working, Needs you, or Ready for review, with issue and PR links, the last handed-back summary, and elapsed time. The Activity sidebar uses the same grouping rule. The Orchestrator instructions ask for a one-line update when T3 reports that a child finished, blocked, or failed.

    All 129 focused tests passed, along with the web type check and free Codex and Claude eval checks. I reproduced the broader check failures on main: three Claude background-work tests, three mobile type errors, and two server type errors. I based the draft on a fresh branch from origin/main because the assigned branch contained an unrelated local commit.

    PR #482, head b579997, checks focused passes and confirmed baseline failures, reviews draft.

  3. tannerpolley commented on Nov 18, 2026

    @tannerpolley
    OwnerAuthor

    T3 Code closeout: done

    Issue: #440 Orchestrator status read and status posts
    Thread: thread:delegated-task:command%3Amcp%3Aaf93ca41-fec6-470a-96c2-8aadf4aef446%3Adelegate-task%3Adelegate-440-2026-11-18
    Model: gpt-6.2-sol
    Branch: issue-440-repository-child-status
    Completed: 2026-11-18T21:02:13.618Z

    Fixed all three Checker findings in PR #482, rebased onto fa938daa98, and pushed to the same branch.

    • Linked-environment children now appear from the parent’s stored task projection, including failures, without polling the linked machine.
    • The SQL excludes archived and deleted local children before ranking summaries.
    • The server and web sidebar now share the approval rollup, so a grandchild’s approval waiting on the owner puts the direct child under Needs you.

    Server vp run typecheck exited 0 with zero errors. Web type checking and both new tool-level tests passed. The broader check recorded 1,158 passing tests and surfaced the three pre-existing Claude adapter failures tracked in #470 and the three known mobile type errors.

    PR #482, head 1290d4f, checks server and web types and new tool tests passed, broader checks hit known failures, reviews draft.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions