Skip to content

[Meta] Dogfood Ace end to end #5

Open
67 of 80 issues completed
Open

Description

@iamnbutler

The team dogfoods Ace together this week, ahead of Universe. This issue is the dogfooding policy and the open backlog. It absorbed #218 on October 15. Closed items were removed; their history stays in the issues and PRs and in this issue's edit history.

Policy

  • All Ace development happens in Ace.
  • Record any external-tool escape in the PR's Built in Ace section and link the gap.
  • File bugs and missing capabilities as issues and link them here.

Items are ordered by importance within each list.

Blocking the team

Core and quality of life

Hosted and cloud channels

The cloud compute pilot is done (#216 closed after scenarios 26 and 26b).

Development loop

Later

These aren't needed to dogfood this week:

Other hosted and cross-host work is tracked in #58. The stable release is #217.

Activity

  1. pinned this issue on Oct 4, 2026
  2. 90 remaining items

  3. iamnbutler commented on Oct 15, 2026

    @iamnbutler
    ContributorAuthor
  4. iamnbutler commented on Oct 15, 2026

    @iamnbutler
    ContributorAuthor
  5. iamnbutler commented on Oct 15, 2026

    @iamnbutler
    ContributorAuthor

    Study scenario 25 (lobby/presence): verified on #17. Filed #406 and #407.

  6. iamnbutler commented on Oct 15, 2026

    @iamnbutler
    ContributorAuthor

    Hosted compute dogfooding evidence for #216 is in draft #416. Two actual hosted Ace model runs used the lane/file/shell tools in Cloudflare, pushed a lane, and continued after filesystem restore and resize. Deployment, lifecycle validation and most checks ran through an isolated source Ace terminal.

    External escapes are recorded in the PR: Codex implementation/orchestration and some initial checks because the harness integration remains #9; Chrome automation for Wrangler OAuth authorization relates to #50. An early Docker check used the external terminal while the installed host was unavailable; later checks used the isolated source host. These existing gaps remain linked here; no new native UI behavior is claimed.

    A lifecycle constraint relevant to #53: a detached child can outlive its shell tool. The pilot now refuses checkpoint/resize while later background processes are still live, rather than claiming that cleanup preserved a consistent filesystem. Both local detached-writer and deployed detached-process refusal checks passed.

  7. iamnbutler commented on Oct 15, 2026

    @iamnbutler
    ContributorAuthor

    Study scenario 26 (cloud compute beta) passes end to end (see #216). Filed #420 and #421.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions