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

Workspace AI lock: block every agent/assistant and hide all AI interaction

Open
  • Is something wrong?
#614 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 18, 2026.

Assessment

This issue has not been assessed yet.

Description

agent:planning enhancement

Founder direction (Hubert, supervising session, 2026-10-18). A workspace can be completely free of AI: no agent or assistant may read it or act in it, including a member’s own personal assistant. Workspace settings must provide the switch; the Agents tab and other AI interaction surfaces disappear while blocked. This is a server-enforced workspace policy.

Milestone: 2 — complete application and release (brief). Extends the foundation’s optional AI/human collaboration and F-016/F-018/F-022/F-027. Persona: a team that wants ordinary human collaboration with AI entirely excluded from this workspace.

Acceptance criteria

  • AC-1 — Workspace control. An authorized workspace administrator can persistently disable/enable AI in workspace settings, on computer and phone. Members without settings authority cannot change it. Reload/reconnect preserves the policy; existing-workspace migration/default and the current state are explicit.
  • AC-2 — Total supported AI access denial. When disabled, all supported agent/assistant entry points are denied both reads and actions: personal assistants, embedded agents, external MCP clients, API-provider runs and official-CLI runtimes, automatic/scheduled/proactive work, bootstrap/orientation, tools and subscriptions. Owner/admin membership, an existing connection, token or standing grant never overrides the block. No blocked workspace content or metadata is supplied indirectly through global discovery/search, context assembly, files/citations, event feeds or caches. Enforce this on the server across all workspace projects, private and DM contexts.
  • AC-3 — Immediate cutover. Disabling fences active/queued runs and existing sessions/subscriptions across API/worker/runtime processes: no subsequent read, model dispatch, streamed delivery, write or result commit may cross the disabled policy. Cancel/stop in-flight work safely; a late provider response cannot publish. Re-enable requires current authority and never silently replays work queued while blocked. Record/test the precise commit/cancellation boundary; no stale-cache grace window.
  • AC-4 — Human-only interface. Hide the Agents tab, personal-assistant entry points, AI buttons/menus/shortcuts, suggestions and AI onboarding within that workspace. Existing tabs/deep links receive a clear blocked state without launching AI. Preserve the settings switch and normal human conversation, tasks, maps, wiki, files, search and collaboration. Preserve existing native work/history; disabling does not delete data. Other workspaces retain their own AI policy and operation.
  • AC-5 — Observable verification. Docker API/worker/runtime/MCP tests cover two owners, administrator/member/agent identities, already-issued grants/tokens, active/queued/scheduled jobs, revoke/reconnect, cross-workspace context and a late in-flight result. Include actual multi-process enforcement and provider-call negative controls. Chromium/WebKit desktop/phone tests verify settings authorization, hidden AI surfaces, direct links, reload and working human collaboration; independently evaluate the final candidate with the bounded review policy.

Ownership and interfaces: single implementation owner @PelikanFix16; independent evaluator @Zamojski5. Coordinate existing #68 personal-assistant runs, #152/#160 external co-work, #153 scheduling, #281 runtime activation, workspace access/settings and Agents UI. These are shared interfaces, not permission exceptions; the workspace block takes precedence. Keep this one coherent outcome, without child-issue fragmentation.

Contract status / next action: founder outcome accepted; queued, implementation not started. Record the workspace policy/cutover contract in product/development docs and obtain one bounded peer assessment before implementation. Existing WIP #612/#613 continues. No founder approval queue. No matching workspace-wide AI exclusion issue was found in the existing backlog.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
19h 9m
Merged PRs (30d)
334

Getting set up

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 ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.