Skip to content

feat: docked assistant panel, system views dropdown, mail relay seam, per-install setup close (abilityai/trinity-enterprise#1291) - #4670

Draft
trinity-ability wants to merge 16 commits into
devfrom
feature/pro-assistant
Draft

trinity-ability wants to merge 16 commits into
devfrom
feature/pro-assistant

Conversation

@trinity-ability

Copy link
Copy Markdown
Contributor

Summary

  • Assistant panel, docked on the left (entitlement-gated, admins only): a slim rail when collapsed, a resizable panel when open; the page sits beside it from 1280px. Its button is the logo in the top-left corner with "Trinity" beside it. Option/Alt+Z opens and collapses it. It speaks first to someone it does not know, holds the getting-started steps, and stays out of the way while the setup overlay is open. Everyone else keeps the help button unchanged.
  • System views are a toolbar dropdown. The Systems column on the dashboard is removed (with the [BUG] Dashboard: the Systems rail takes 60% of a phone screen and squeezes the fleet into ~150px #4521 phone-rail tests that only existed for it); the activation checklist floats in the dashboard's bottom-left corner where there is no panel to hold it.
  • Mail relay seam in email_service: with no mail provider, a registered module may deliver a sign-in code or an invitation. A configured provider always wins; nothing registered means no change. A relay that refuses leaves no code in the log.
  • Setup is offered again on a fresh install. "Setup closed" is kept against a short mark of the install (install on GET /api/onboarding/first-run, read with the non-minting accessor).
  • An agent tile that has never run shows the outline of its charts.

Changes

  • src/frontend/src/components/assistant/AssistantWidget.vue, stores/assistant.js, utils/assistantCards.js, utils/assistantStarters.js, App.vue, NavBar.vue, HelpChatWidget.vue
  • src/frontend/src/components/SystemViewsMenu.vue (new), SystemViewsSidebar.vue (deleted), views/Dashboard.vue
  • src/frontend/src/components/onboarding/{FirstRunOverlay.vue,firstRunSteps.js}, stores/firstRun.js
  • src/backend/services/{email_service,agent_invite_service,onboarding_service}.py, models.py
  • Docs: feature flows (onboarding wizard, agent tags), architecture (API endpoints, backend), requirements (auth, roadmap), UI test sheet PHASE_36, a learnings fragment, /cso --diff report

Test Plan

  • pytest tests/unit/test_email_relay.py tests/unit/test_ent319_first_run_front_desk.py tests/unit/test_2669_minting_accessor_callers.py (82 passed with the neighbouring guards)
  • Frontend unit: assistant, first-run, dashboard, nav, help widget, agent tile, and the raw-colour / source-text / loading-gate ratchets (257 passed)
  • Guards that import the real app (route census, ops-write sweep) could not run on the author's machine; they must be green in CI
  • Manual: sign in as admin on a fresh install; setup overlay opens, the panel stays collapsed until it closes, then opens beside the page
  • Manual: dashboard at 1440px and 390px with the panel open and collapsed, light and dark

Notes for review

Refs abilityai/trinity-enterprise#1291, abilityai/trinity-enterprise#1283

🤖 Generated with Claude Code

trinity-ability and others added 16 commits November 18, 2026 14:52
…y-enterprise#1283)

An entitled admin gets an assistant panel in the corner launcher in place
of the help widget; everyone else keeps the help widget unchanged.

- AssistantWidget + assistant store: a door to choose how the assistant is
  served, the conversation, and the plan line reported by the instance.
- assistantContext: each turn carries the page, the fleet and the
  conversation, read with the person's own session.
- assistantCards: a change the assistant proposes becomes a card. It is
  accepted only if its action is in a fixed catalog and every agent it
  names is one the page read; Confirm makes the change through the app's
  own route and reads the result back.

Prototype. Unit and mounted tests included.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…as a tab (Abilityai/trinity-enterprise#1283)

The panel sends each message to the instance's assistant routes and follows a
turn step by step. A proposed change or a design is a card the person
confirms. The help widget can be embedded, and is the panel's second tab.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…long work (Abilityai/trinity-enterprise#1283)

- Dashboard: an agent made while the page is open lands in its cell (socket,
  snap spring, ring, sheen, a New tag that stays a few seconds); the list
  view glows the row once. Keyed off a store signal that ignores first
  loads, lifted filters and roster swaps.
- Assistant panel: progress cards for builds and runs with elapsed time, a
  step trail during a turn, a launcher badge when an answer arrives while
  closed, grouped starters for the page and fleet, replies as full-width
  boxes, a multiline composer, and a one-click terms step before the first
  message.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…s no provider (Abilityai/trinity-enterprise#1283)

email_service gains a relay seam (register_relay / clear_relay). With no mail
provider configured, a sign-in code or an invitation is handed to the relay if
one is registered and says it can deliver; can_deliver() counts it. With no
relay, behaviour is unchanged. send_html takes the kind and fields a relayed
mail needs; the agent invitation passes them.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
… closed it before (Abilityai/trinity-enterprise#1283)

"Setup closed" was one flag per browser, so a reinstall at the same address
inherited the old close and never showed setup. GET /api/onboarding/first-run
now returns a short opaque mark of the install and the close is remembered
against it. A bare '1' still counts as closed, so an upgrade reopens nothing.
The overlay also publishes that it is open, for other surfaces on the page.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…bilityai/trinity-enterprise#1291)

The Systems column down the dashboard's left edge is replaced by a toolbar
dropdown (All agents, each view with its count and an edit control, New
system view), so it no longer takes width from every pane. The activation
checklist it carried floats in the dashboard's bottom-left corner, still out
of the page flow. Baselines lowered for the deleted file and the one source
read the spec no longer makes.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
… its charts (Abilityai/trinity-enterprise#1283)

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…d holds the getting-started steps (Abilityai/trinity-enterprise#1291)

- Docked on the left of every page: a slim rail when collapsed, a resizable
  panel when open (the page sits beside it from 1280px). Its button is the
  logo in the top-left corner with "Trinity" beside it; Option/Alt+Z opens
  and collapses it; Enter sends.
- Speaks first to someone it does not know, tells a new install's example
  agents from the person's own, and stays out of the way while setup is open.
- Holds the getting-started steps; drops a conversation kept from an earlier
  instance; shows what is left of the allowance and when it comes back.
- One button in the corner: the help widget waits until it is known which
  this person gets.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
# Conflicts:
#	src/frontend/src/components/SystemViewsSidebar.vue
#	src/frontend/tests/unit/firstRunSteps.spec.js
…links (Abilityai/trinity-enterprise#1283)

- The install mark is read with the non-minting accessor: a GET must not
  create the installation id (#2669). A close kept for another install never
  counts, and a close made before the install has a mark is re-kept against
  it once it does.
- A confirm card says "cannot be undone" only for changes that cannot.
- A link supplied from outside is used only when it is a plain web address.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…a denylist (Abilityai/trinity-enterprise#1283)

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…ocs for the changed surfaces (Abilityai/trinity-enterprise#1283)

A code written to the log is one hop from whoever reads the logs. The
console provider still prints codes because an operator chose it.
Architecture and the UI test sheet follow the relay seam, the install mark
and the removed Systems column.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@trinity-ability trinity-ability added the ui PR touches the frontend UI — triggers Playwright e2e tests label Nov 19, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ui PR touches the frontend UI — triggers Playwright e2e tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant