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

F-027 A1 — Assistant identity, switches and settings

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

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 9, 2026.

  • #457 by @PelikanFix16 — open

Assessment

This issue has not been assessed yet.

Description

Slice A1 of F-027 (founder direction 2026-10-09; contract PR #401). The AST criteria referenced below are defined there and are this issue's acceptance criteria.

  • Scope. One owner_assistant agent connection per person per workspace,
    created in the same transaction as the assistant's enablement, with its S6 policy
    initialised in that transaction. A settings record: approval mode (act default,
    ask), changes per run, background runs per day. Owner-only GET/PATCH with
    If-Match/CAS. The area mapping of AST-4 lives in one contracts module and compiles
    areas into S6 capability and entry IDs; Only read drops the operations.
  • Files. app/packages/contracts/src/assistant.ts (areas, plain labels, mapping
    from AGENT_MCP_ENTRIES); app/packages/core/src/assistant/ (settings use cases);
    app/apps/server/src/assistant/routes.ts; the enablement path in
    app/packages/core/src/personal-runs/service.ts.
  • Migration 0077 assistant_settings: add owner_assistant to the
    compute_source CHECKs of agent_connections and agent_proposals; table
    assistant_settings (workspace, owner, agent connection, approval mode CHECK,
    limits CHECK, version, timestamps); reverse file; semantic-footprint entry.
  • Joining. Turn on creates contributor project grants for the assistant in the
    projects the owner manages (and later in projects the owner creates), through the
    existing project-grant route; the join request for other projects reuses the Agents
    Request row (AST-3.4).
  • Tests. App tests for AST-3.1, AST-3.3 (reuse S6 race helpers), AST-3.4, AST-4.1
    (API part), AST-5.1 (API part); migration fresh/upgrade/reverse.
  • Depends on. PR #390 merged (S6 overlay, migration 0061).

Rules: Docker tests with fakes/mocks only (no real vendor account, key or spend); final design (Prostota) components; UX reviewed against F-027's journeys by an independent evaluator in the running app.

Implementation seam clarification, 2026-10-10 (bounded A1 follow-up): current main/#347 has no persisted project-agent join-request backend. AST-3.4 retains the same owner/request/manager-grant behavior; A1 supplies a durable pending join-request record under migration 0077, an authorized Request projection/manager response using the existing project-grant use case, and one Needs-you notification for the project's current managers. Asking never grants authority. A caller must retain project read access, and no manager/project information outside those read rights is revealed. No assistant grant is automatically added where the owner lacks project.manage. The five switches/settings/identity criteria remain unchanged. The previous phrase "existing Request row" referred to the drawn presentation, not an implemented persistence seam.

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

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.