Skip to content

Rebuild first-run onboarding around Exie - #2736

Open
ejsmith wants to merge 45 commits into
mainfrom
feature/exie-onboarding
Open

ejsmith wants to merge 45 commits into
mainfrom
feature/exie-onboarding

Conversation

@ejsmith

@ejsmith ejsmith commented Nov 19, 2026

Copy link
Copy Markdown
Member

Rebuilds first-run onboarding around Exie so a new user goes from signup to their first event, and knows what to do next, without getting stuck. Stacked on the blockers PR; merge that one first.

Changes

flowchart LR
  S[Sign up / log in<br/>redesigned with Exie] --> P[Name project]
  P --> C[Pick platform<br/>copy-ready snippet]
  C --> F{First event?}
  F -- waiting --> W[Exie: I'm listening<br/>sample data + troubleshooting]
  F -- arrives --> Y[Confetti, open the event]
  Y --> K[Exie's checklist]
Loading
Area What's new
Signup and login Exie hero. Trial-aware tagline. Signed-in users can accept invites. OAuth server errors are shown.
Setup Project comes first, then a stepper and platform picker. Retries are safe. The first event is celebrated live.
Empty states Exie's empty states on list pages. First-run users without events land on setup. Filtered lists say "No events match these filters."
Exie's checklist 8–9 items (Ask Exie appears where Exie is available). Collapses to one "Next:" row after the first event. Finishing celebrates and retires it; X hides it for good.
Verification A verified user lands back in the app. A link opened for another account says so.
Notices One setup prompt at a time, shown before trial or usage notices.
Cache Membership, project create, rename, and delete refresh lists without a reload.

Breaking changes and deploy notes

  • None. New checklist state uses the existing product-tour records (checklist-*).

Testing

  • npm run validate is clean. 1,386 unit tests pass.
  • The full backend suite passes (3,830 passed, 28 skipped).
  • New e2e coverage: checklist finish, dismiss, and next-link; first-run empty states; setup landing; and verification landing. The full e2e run passes when run on a single worker (parallel runs hit the 10-signups-per-hour limit).
  • A manual walkthrough covered signup, ASP.NET Core setup, the first event, and a trial at 14 days, 2 days, and ended.

ejsmith and others added 30 commits October 21, 2026 12:34
Marking a project configured after its first event used an id-only patch.
That notification carries no organization id, so the web socket broker
dropped it and onboarding prompts stayed stale until a manual refresh.
Publish the change with the project's organization while still patching
only is_configured, and make it searchable before clients refetch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The verify page posted to a route that does not exist, so every emailed
verification link failed. Call the GET endpoint with the token as an
encoded path segment, explain missing, invalid, used, and expired links,
and refresh the current user so the "Email not verified" prompt clears.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The add project form now submits with "Continue to Client Setup".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Free organizations with no projects saw the free plan upsell instead of
the prompt to add a first project. Order organization notices so account
problems come first, then setup steps, then upgrade prompts. Also fix the
"Set up" wording and keep only one playful line across the setup notices.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every 401 from login or signup showed "Invalid email or password",
including rate-limit denials. Use the existing problem titles to tell
users when they need to wait, and to say when a signup email already has
an account. Response status codes and shapes are unchanged; endpoint tests
now pin the titles the forms rely on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The only signup email read like an account activation gate. New accounts
now get a short welcome that says the account already works, that
confirming turns on email notifications, that the link expires in 24
hours, and where to go next. Resent and changed-address confirmations
keep a plain confirmation message without the welcome.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Exie is drawn from the ExieIcon geometry (copied unchanged from the
assistant branch so both merge cleanly) with hello, idle, listening,
thinking, and celebrate moods. Motion is CSS-only and stops under
prefers-reduced-motion while each mood stays readable. The speech
bubble carries real text and announces changes politely; the mascot is
hidden from assistive technology.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signup gets a two-column layout with Exie and the setup plan, a real
heading, inline-only validation, a password visibility toggle, and an
autofocused name field. Login says "Welcome back" and links to "Create
an account" instead of a trial that does not exist.

Both pages keep ?redirect= and ?token= through each other and through
OAuth, and invited users land in their organization. An existing
session is no longer ended silently: without an invitation the page
continues into the app; with one, the user chooses Continue or Sign
out, and a failed sign-out still clears the local session so the form
is never left inert. OAuth buttons show progress, report blocked or
closed popups and rejected exchanges, and fill the grid for any number
of providers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Exie greets the user by first name and asks what the app is called
before the organization, which is prefilled from a company email
domain or as "{FirstName}'s Team" for personal mailboxes. Names are
trimmed and whitespace-only values are rejected before any request.

If the organization is created but the project fails, a retry reuses
that organization instead of creating another one (which the plan
limit rejects). The setup shell gains a top bar with "Not {email}?
Sign out" and, for users who already have an organization, Cancel.
Add Project shares the look and validation. The project-configure tour
now starts on the project name to match the new field order.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The configure page replaces the project type dropdown with a searchable
platform grid: popular platforms first (now including Worker Service,
React, Vue, and Angular) and older .NET Framework entries collapsed.
Every previous ?type= value still opens its platform; ?type=bash maps
to the new REST API (curl) entry.

Snippets were checked against Exceptionless.Net 6.2 and the 3.2 npm
clients: current ASP.NET Core and hosting registration, optional
logging integration, code-based WPF/WinForms keys, no --save, no
top-level await, and a "send a test error" step for every platform.
Raw HTTP examples send an @simple_error event that stacks by message.

The API key has its own card with copy, loading, retry, and distinct
disabled/suspended states. Self-hosted installs without a configured
server URL get the API origin instead of a placeholder or the hosted
collector. Exie listens whenever the project has no events, offers
platform-specific troubleshooting after a minute, and can add sample
data after confirmation. The first event no longer redirects into a
possibly empty list: confetti and Exie celebrate, and the dialog shows
the event with "Take me to it" and "See all events". Guided tour
completion is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New organizations see a collapsible, dismissible checklist above Stacks
and Events: account, project, and first event come from data; email
verification follows the account and offers Resend; notifications,
MCP/AI tools, inviting the team (noted as a paid-plan feature on Free),
and versions & environments complete when opened. Progress is stored
through the existing per-user product tour records, so no new API is
needed. When everything is done, Exie says "You're all set!".

The generic "Welcome to Exceptionless" card no longer appears
automatically while the checklist is active, and dismissing the
checklist also retires that card. Tours stay available from Help.
E2E scenarios dismiss the checklist by default, like the welcome card.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Stacks, Events, and the Stream show "Nothing yet — I'm listening!"
with Continue setup and Explore with sample data while the organization
has no events. The check combines the project flags, live event
notifications, and the organization event count, so a lagging
is_configured flag never hides real events. Those pages skip the
duplicate "We haven't received any events yet" notification. Filtered
lists with no results now say "No events match these filters."

Opening / in an organization where no project has received events goes
to that project's client setup (or Add Project) instead of an empty
Stacks view filtered to errors.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The logo stretched as a column flex child; size it by height with an
auto width on every onboarding page. Exie is larger on signup, both
columns sit centered vertically, and each plan step gets a one-line
description.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Stacks, Events, and the Stream already show Exie's empty state with
Continue setup, so the organization banner no longer adds "Set up your
first project" or "We haven't received any events yet" there. While the
page owns the setup prompt, the free-plan upsell stays hidden too, which
keeps setup ahead of upgrades.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Choosing a platform folds the grid into a single "Your platform" row
with Change, then scrolls the instructions into view (instantly under
reduced motion) and moves focus to their heading. Links with ?type=
open collapsed. Change reopens the grid with the search focused, and
Keep returns to the row.

After a minute without an event, Exie switches to "Taking a while?
I've got a few tips." with a Show me button, and "Not seeing anything?"
appears closed instead of pushing the page down.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Once an event has arrived, the checklist shows a single row: Exie,
progress, "Next:" linking to the first open item, and an expand
chevron. Before the first event it stays fully open beside the empty
state. Each user's expand or collapse choice is remembered on this
device.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An invitation can only be accepted while logging in or signing up with
its token, and existing members are added to organizations directly,
so an invitation link opened while signed in is for another account.
The notice now leads with "Sign out and accept invitation", which keeps
the token and shows the form, and offers "Continue as {email} without
accepting" instead of a Continue that silently dropped the invitation.

OAuth failures now show the server's explanation whether the request
throws ProblemDetails (the app's request options) or FetchClientError.
Page tests cover both invitation choices, a failed sign-out, and the
redirect for a signed-in visitor without an invitation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The default landing now sends a user to setup only when the onboarding
check (project flags, live notifications, and the organization event
count) says no events have arrived, and waits until that is known. The
layout hides setup prompts and upsells only while a list page actually
shows Exie's empty state, so an organization without projects but with
older events still gets a prompt. The celebration stops looking for the
new event after 30 seconds and falls back to "See all events".

Tests cover the setup retry reusing the organization (one organization
request), whitespace-only names, the email-domain suggestion, and the
default landing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
First-run setup creates an organization and project, then lists the
organization's projects. The list could be fetched before Elasticsearch
indexed the new project, so it came back empty and stayed cached: the
"Set up your first project" banner and Exie's checklist kept showing
after setup and even after the first event. Create both with immediate
consistency, and add the new project to every cached project list for
its organization.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The email field checks availability with a one second debounced async
validator, and TanStack Form treats the form as unsubmittable while a
field is validating, silently dropping the first submit. Clicking
"Create account", pressing Enter, or password-manager autofill within
about a second of editing the email did nothing.

submitWhenValidated waits for any pending field validation and then
submits, so an "email already exists" result still blocks the submit.
Signup and the Account settings email form use it, including the
settings form's own debounced autosave.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new organization is on the free plan by definition, and its first
event arrives within minutes, so the banner turned the first reward
moment into "Upgrade now" and then sat on every page. It now waits
until the organization is seven days old. Suspension, overage, request
limit, setup, and premium-feature banners are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On Stacks, Events, and the live stream, Exie's "I'm listening" empty
state was silently replaced by the table when the first event arrived.
The app layout now shows a "Your first event just landed!" toast, with
a View events action unless the user is already on Events.

It fires only when the page saw the organization go from waiting to
having events, so loading a page that already has events, leaving and
coming back, or switching organizations stays quiet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After a successful email verification the page went to Account
settings, away from the onboarding flow. It now goes to the app root,
which routes first-run users to setup or their events, so Exie's
checklist shows "Verify your email" ticked. Failed verifications still
go to Account settings, where their toasts say to resend the email.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
getProjectsQuery nested the projects key inside another array, so
TanStack's partial matching never matched ['Project', ...] filters and
creating, renaming, or deleting a project, or a ProjectChanged
message, never refreshed the project list or notification settings.
The other project and organization keys are already flat.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…vents

Deleting a project only invalidated its own query, so organization
project lists kept showing it until they refetched. The delete now
drops the ids from every cached organization list, the way creating
a project adds them, then invalidates the project queries.

The organization's event count lags asynchronous event deletion, so
onboarding could report received events for an organization with no
projects. hasReceivedEvents now requires at least one project.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…zation

The UserMembershipChanged handler was commented out, so an existing
user who was invited to an organization, or removed from one, kept a
stale organization switcher, "/" redirect, and command palette. The
app now refreshes the organization's member list for everyone in it,
and for the affected user also the organizations list and users/me.
After a removal it marks the organization's own queries stale without
refetching them, so the layout can move the user to another one.

The server removed the user's connections from the organization group
before sending the message, so the removed user never received it.
MessageBusBroker now also sends it to their connections directly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Clients list the organization's projects right after renaming or
deleting one, but both writes returned before Elasticsearch indexed
them, so the list could show the old name or the deleted project.
Use immediate consistency, as creating a project already does.

A rename followed by an immediate list reproduces the stale name
without the change. A delete followed by an immediate list did not
reproduce a stale project in the test environment, so the change is
covered only by the rename test.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The login page said "By signing up" under a log-in form, so it now
says "By continuing"; signup keeps its wording.

Signup, the setup page, and the configure page had no title: the root
layout sets the title from navigation items and resets everything
else to "Exceptionless", which also overwrites a title set in the page
itself. The layout now has a small table of titles for these pages
("Sign up", "Set up Exceptionless", "Send events").

The checklist item "Turn on notifications" suggested notifications
were off, but new projects already email new errors and a daily
summary, so it is now "Review your notifications" and says so. Its id
and storage key are unchanged.

The configure page hides "Back to Project Settings" during first-run
setup (redirect=true), since a new user never came from there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…as clicked

Finishing every item now celebrates with confetti and a toast, then records the checklist as done so it
never comes back, instead of leaving a "You're all set!" card up for 30 days.

Clicking an item marked it done synchronously, which re-rendered the "Next" link to the following item
(or swapped the row's link for plain text) before the router read the href. "Next: Review your
notifications" went to AI tools and ticked notifications without the user ever seeing that page.
The local done mark now waits until the click is handled.

Adds component tests and e2e coverage for finishing every item, the next link, and dismissing for good.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An already-verified user reopening the link gets the verified toast and the app, not Account settings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…kers

# Conflicts:
#	src/Exceptionless.Web/Api/Handlers/OrganizationHandler.cs
#	src/Exceptionless.Web/Api/Handlers/ProjectHandler.cs
#	src/Exceptionless.Web/ClientApp/e2e/fixtures/api-client.ts
#	src/Exceptionless.Web/ClientApp/e2e/tests/email-verification.e2e.ts
#	src/Exceptionless.Web/ClientApp/src/lib/features/organizations/components/organization-notifications.svelte
#	src/Exceptionless.Web/ClientApp/src/lib/features/organizations/components/organization-notifications.svelte.test.ts
#	src/Exceptionless.Web/ClientApp/src/routes/(app)/account/verify/+page.svelte
#	src/Exceptionless.Web/ClientApp/src/routes/(app)/account/verify/verify-page.svelte.test.ts
# Conflicts:
#	src/Exceptionless.Web/Api/Handlers/ProjectHandler.cs
#	src/Exceptionless.Web/ClientApp/e2e/support/exceptionless-journey.ts
#	src/Exceptionless.Web/ClientApp/e2e/support/page-helpers.ts
#	src/Exceptionless.Web/ClientApp/e2e/tests/email-verification.e2e.ts
#	src/Exceptionless.Web/ClientApp/src/lib/features/auth/index.svelte.ts
#	src/Exceptionless.Web/ClientApp/src/lib/features/organizations/components/organization-notifications.svelte
#	src/Exceptionless.Web/ClientApp/src/lib/features/organizations/components/organization-notifications.svelte.test.ts
#	src/Exceptionless.Web/ClientApp/src/routes/(app)/account/verify/+page.svelte
#	src/Exceptionless.Web/ClientApp/src/routes/(app)/project/[projectId]/configure/+page.svelte
#	src/Exceptionless.Web/ClientApp/src/routes/(auth)/login/+page.svelte
#	src/Exceptionless.Web/ClientApp/src/routes/(auth)/signup/+page.svelte
Invited users who sign up with a different address still get a confirmation
email, but they join an organization that already has apps, so the "connect
your app" next step doesn't apply. Also stop the email implying confirmation
only turns on notifications.
- Land on the default view when the project list fails to load instead of
  waiting on a blank root page forever.
- Reset the client setup page's first-event state when only the project
  changes, so one project's celebration doesn't carry over to the next.
- Let pages with their own setup prompt still show trial, usage, and upgrade
  notices instead of an empty slot.
- Only extend or trim cached project arrays when a project is added or deleted.
- Wait for a possible duplicate WebSocket send before counting messages.
- "Your free trial for Acme ends in 2 days." instead of "The Acme free trial
  ends in 2 days ." (TimeAgo no longer adds a space before punctuation).
- The sidebar says "Trial ended" once the end date passes, before the
  expiration job moves the organization to Free.
- Hosted signups say "Try every feature free"; the checklist explains that
  verifying unlocks Exie and team invites during a trial.
- Sentence-case the client setup heading.
Verified users continue into the app, signed-in visitors to login and signup
go back to the app, and a fresh user without events lands on client setup.
Assert the actual landing page, seed an event where a spec needs Stacks, and
skip the Mailpit-based checklist spec in production.
Invited users who sign up with a different address still get a confirmation
email, but they join an organization that already has apps, so the "connect
your app" next step doesn't apply. Also stop the email implying confirmation
only turns on notifications.
The organization key prefix also matches non-list queries, so check for an
array before appending. Also apply formatting to the merge resolutions.
Organizations without events show Exie's empty state and open client setup,
so specs that need Stacks or table columns seed an event first, and filtered
empty lists say "No events match these filters."
# Conflicts:
#	src/Exceptionless.Web/ClientApp/src/lib/features/users/api.svelte.ts
The item opens Exie with a prompt about the most recent error and checks
itself off. It is listed only where Exie is available, or will be once
the email is verified, and waits for the first event.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-19T00:16:45.780330Z b88b0eb New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7804ed011c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Remember that this visit saw the project waiting, so a project refresh
that lands before the event notification still opens the celebration.
Give the new onboarding and auth tests explicit Arrange, Act, and Assert
sections.
Base automatically changed from issue/onboarding-blockers to main November 19, 2026 04:50
The server records a session start alongside the first event from an
identified user, and it can win the newest-event lookup. Skip session
tracking events so the dialog and its link point at the real event.
@github-actions

Copy link
Copy Markdown

Code Coverage

Package Line Rate Branch Rate Complexity Health
Exceptionless.AppHost 23% 22% 130 ❌
Exceptionless.Core 78% 70% 11215 ✔
Exceptionless.Insulation 51% 43% 370 ➖
Exceptionless.Web 87% 74% 10320 ✔
Summary 81% (29992 / 36872) 71% (15339 / 21590) 22035 ✔

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant