Teach how Ace works and what sharing exposes on first run
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Funcionalidade
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- typescript
- Domínio
- documentation, frontend
Direção de pesquisa
The payload names no source files, so start with docs/terms.md for the vocabulary and the README to see how the product is described now. Find the existing first-run and the sharing, channel and project controls in the app. The checklist defines what the copy must cover. Related work is #214 (the collaborator-invocation toggle) and #162 (non-Git folders), so check those before writing. Done means each checklist item appears in a short first-run sheet or inline on its control, in terms.md vocabulary.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
New users don't know how Ace works or what sharing exposes. Teach it in the product, not only in the README: a short first-run sheet plus inline copy on the controls, not a tour. Use the terms vocabulary.
Already done
- Sharing toggle states what it grants (#243, #389): "Teammates can run commands as you on this machine, with Ace's macOS permissions such as Screen Recording." Cloud compute channels name the container instead (#422). Verified in study scenario 6.
- Desktop tools toggle: its tooltip names owner and collaborator runs, and turning it off says shell still has Ace's macOS permissions (#380). A refused call tells the agent to ask the owner (#258).
- Non-Git folders (#162): Cmd+O offers
git initand explains that lanes are Git worktrees (#222,apps/app/src/open-project.tsx). - Where a channel lives is shown in channel details: Host, Hosted plus Workspace, or the cloud container (
apps/app/src/placement.ts,channel.tsx, #422).
Remaining
- First-run sheet that covers each of these in a line:
- Your machine is the host. Channels and agents run on this Mac as you. Lanes are Git worktrees, not sandboxes.
- Your tailnet is your team. Everyone on the tailnet running Ace can see your channels and their history. There are no Ace accounts or invitations. This was the least understood rule in the study (1/3, scenario 1).
- Sharing gives teammates your machine. Teammates can invoke agents only when you turn agent access on. Desktop tools are a separate owner toggle.
- Where a channel lives: local, a teammate's host, hosted, or cloud compute.
- Projects vs. channels: Cmd+O adds a project; creating a channel is a separate action.
- Say on the channel, or near the channel list, that tailnet teammates can see it. No in-app copy says this today.
- Say that only the owner controls agent access and desktop tools, instead of leaving people to infer it from a disabled control (scenario 1).
- Decide whether turning desktop tools on gets a confirmation like agent access does (scenario 7).
- Re-run the scenario 1 explain-back after this ships. The baseline on 0.0.26 was 1/3 for visibility and 2/3 for everything else.
Part of #217's pre-Universe list.
- Linguagem predominante
- TypeScript
- Estrelas
- 1
- Forks
- 0
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Sem guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de githubnext/ace2
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 94/100
githubnext/ace2#487 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 90/100
githubnext/ace2#486 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
githubnext/ace2#459 ·
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 88/100
githubnext/ace2#437 ·
-
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
githubnext/ace2#442 ·
Todas as issues de githubnext/ace2
Issues semelhantes
-
e2e-failure ready-to-code
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
redhat-developer/rhdh-plugin-export-overlays#4460 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
Mantenedores costumam responder em até 1 dia
-
docs(api): openapi.yaml still documents gif-tools optimize colors as 2-256 instead of 2, 4, 16, 256Abertaarea: backend documentation priority: low
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
snapotter-hq/SnapOtter#2919 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
obsidianmd/pele#39 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
biomejs/biome#12475 · 1 comentário ·
Mantenedores costumam responder em até 1 dia