Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Create hosted channels from the new-channel picker

Open
#177 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start by reviewing the deployed pilot findings in #176, the lifecycle work in #13, and the existing channel UI, shared protocol types, and CLI hosted-channel behavior mentioned in the issue. Then trace the app’s project and channel creation flows and owner setup flow. Done means the acceptance checks pass in the native app against a deployed service and real model, including workspace connection, retry, reconnect, and file placement.

Written by the indexing model from the issue text.

Description

Let people create a hosted channel directly from the app. Today the new-channel picker offers This Mac and Run in cloud (cloud compute, #216). A hosted channel with its workspace on this Mac is only reachable by creating it locally and then using Move to, or with ace new --hosted <url>.

Already done

  • Joining the team directory, and saving its secret, from Settings (#350).
  • Details show where a hosted channel runs and what waits for its workspace (#357).
  • Short reasons when the service or the directory fails (#393).
  • Moves show their progress (#375).

Remaining

  • Add a "Hosted on " option to the new-channel place picker (apps/app/src/dashboard.tsx PLACES) when a channel service is known. It creates the channel in that cell, with this checkout as its workspace.
  • Explain clearly when no service is configured or the service refuses.

Create-then-Move-to stays acceptable until this lands.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/ace2

All issues in githubnext/ace2

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.