You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Start new channels with collaborator agent invocation off #214
New channels start with collaborator agent invocation on and native desktop tools on (packages/channel/src/channel.ts:57). Sharing a channel therefore lets every tailnet teammate run shell commands and computer use on the owner's machine, and nothing in the app says so.
Before Universe, choose and ship safer defaults:
New channels start with shared: false: teammates can read and post, but not invoke agents. The owner opts in from the header toggle or ace share <channel> on.
Decide whether desktop also starts off for new channels. The setting is channel-wide, so it affects the owner too.
Existing channels keep their stored settings. A default changes initial, not migrate.
New channels now start with desktop tools off as well (#258). A refused desktop call tells the agent to ask the owner to turn on Channel desktop tools in the channel header. Existing channels keep their stored setting.
Existing channels keep their settings:migrate keeps the stored shared value, and channels with no stored settings use LEGACY (shared, desktop on). This was checked against an isolated data directory from the previous build (docs/data.md, "unshared-default check").
Docs:README.md and docs/architecture.md#the-team now say new channels start unshared, with desktop tools off.
Follow-up from study scenario 7: turning desktop tools on has no confirmation, unlike agent access. If that's wanted, it belongs with first-run teaching in #215.
Activity
feat: start new channels unshared and state what sharing grants (#243)
iamnbutler commentedon Oct 15, 2026
New channels now start with desktop tools off as well (#258). A refused desktop call tells the agent to ask the owner to turn on Channel desktop tools in the channel header. Existing channels keep their stored setting.
feat(host): turn a channel's desktop tools on or off from the CLI (#262)
iamnbutler commentedon Oct 15, 2026
Closing: every item has shipped.
163271e).packages/channel/src/channel.tsinitialis{ shared: false, desktop: false }.09f392d).migratekeeps the storedsharedvalue, and channels with no stored settings useLEGACY(shared, desktop on). This was checked against an isolated data directory from the previous build (docs/data.md, "unshared-default check").apps/app/src/channel-access.tsx, feat: start new channels unshared and state what sharing grants #243, fix(app): mention Ace's macOS permissions in the sharing tooltip #389). For cloud compute channels it names the container instead (fix(app): describe cloud compute channels' container workspace #422). Tester A judged it clear in study scenario 6.README.mdanddocs/architecture.md#the-teamnow say new channels start unshared, with desktop tools off.Follow-up from study scenario 7: turning desktop tools on has no confirmation, unlike agent access. If that's wanted, it belongs with first-run teaching in #215.