Teach how Ace works and what sharing exposes on first run
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 35/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- typescript
- Bereich
- documentation, frontend
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 1
- Forks
- 0
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Kein Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus githubnext/ace2
-
documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
githubnext/ace2#530 · 1 Kommentar ·
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
githubnext/ace2#437 ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
githubnext/ace2#529 ·
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 45/100
githubnext/ace2#528 ·
-
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 20/100
githubnext/ace2#511 ·
Alle Issues in githubnext/ace2
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
getsentry/sentry-conventions#732 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
status:in-linear status:team-assigned team:nodes
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
n8n-io/n8n#41548 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
motiondivision/motion#3955 ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
equinor/prisma-decision-web#919 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 83/100