[Meta] Extend work across hosts and devices
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- distributed-systems
Research direction
This is a meta tracker, not a work item: read the baseline scope in issue #5 first, then choose one linked sub-issue (#49, #11, #15, #57, #13, #14 or #18) and do the work there, not here. Each sub-issue carries its own scope; notes like 'merged in #157' or 'draft #160' tell you which ones are already underway. Done here means a maintainer checks the box after the sub-issue lands with its acceptance criteria met.
Written by the indexing model from the issue text.
Description
Work across hosts and devices, beyond the dogfooding backlog in #5. Items are ordered by importance.
- #57: agents discover and message channels on other hosts, both local and hosted (#180 folded in).
- #11: terminals from the owner's other machines, from teammates, and in cloud containers.
- #49: move a whole channel (state and files) to another Mac. After Universe.
- #18: verify real-phone use.
Hosted channels (the #13 meta is closed; these are standalone issues):
- #177: create hosted channels from the new-channel picker.
- #179: manage hosted channels while their workspace is offline.
- #429: recover channel moves from interruption and retries.
- #182: browser access without a host gateway (later).
Cloud compute (the #216 pilot is done):
- #430: show the stopped state after the service's idle stop.
- #413: keep workspace files beyond the checkpoint limit and across the idle stop.
- #414: let agents see compute usage and request a bounded resize.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/ace2
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 40/100
githubnext/ace2#440 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
githubnext/ace2#430 ·
Similar issues
-
area:security documentation effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
app:web meta:ops
Difficulty 2/5 Half a day Newbie friendliness 78/100
osu-tournament-rating/otr#1113 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
typegoose/mongodb-memory-server#1040 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 92/100