Add survey to Onboarding Users by jfcsantos · Pull Request #171 · Kilo-Org/cloud

jfcsantos · 2026-02-13T11:27:46Z

Summary

Add welcome survey modal using Typeform that displays for new users on the profile page
Survey shows after user signup only. Once submitted or dismissed we store it in db and never show it again.
Track survey completion status in the database to only show the modal once
Integrate with tRPC to persist completion state

Changes

New component: WelcomeTypeformModal - embedded Typeform widget in a responsive modal dialog
Database: Added completed_welcome_form boolean column to kilocode_users table
API: New markWelcomeFormCompleted tRPC mutation to record when users complete/skip the survey
Profile page: Conditionally render the modal for users who haven't completed the form

Implementation Details

Modal prevents accidental dismissal (blocks outside clicks and escape key)
Handles both form submission and skip/close actions
Includes error handling with retry capability if the API call fails
Passes user email as a hidden field to Typeform for tracking
Typeform link: https://admin.typeform.com/form/xNTrQO4E/create?block=18842f7b-22e5-489b-955a-e7d8483656bd

kiloconnect · 2026-02-13T12:37:34Z

src/components/profile/WelcomeTypeformModal.tsx

+    <Dialog
+      open={isOpen}
+      onOpenChange={open => {
+        if (!open) handleSkip();


WARNING: Closing the dialog marks the welcome form as completed

onOpenChange calls handleSkip() whenever open becomes false, and handleSkip() calls markWelcomeFormCompleted. That means a user can be persisted as completed_welcome_form=true without ever submitting the Typeform (e.g. clicking the X). If this is intended, consider renaming the mutation/state to reflect “dismissed” rather than “completed”; otherwise, only call the mutation from onSubmit.

kiloconnect · 2026-02-13T12:37:34Z

src/components/profile/WelcomeTypeformModal.tsx

+      }}
+    >
+      <DialogContent
+        className="h-[50vh] max-w-[90vw] overflow-hidden p-0 sm:h-[400px] sm:max-w-xl [&>button]:rounded-md [&>button]:p-2 [&>button]:text-black [&>button]:transition-colors [&>button]:hover:bg-black/10 [&>button]:hover:text-black/60"


WARNING: Close button styling likely breaks dark-mode visibility

The DialogContent class overrides the direct child button styles with [&>button]:text-black / hover:text-black/60. Since the app is dark-mode only, this can make the close (X) control very low-contrast or effectively invisible on a dark dialog background. Consider using text-foreground (and matching hover colors) or removing the forced text color override.

kiloconnect · 2026-02-13T12:37:56Z

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (10 files)

src/app/(app)/profile/page.tsx
src/app/api/cloud-agent/sessions/prepare/route.test.ts
src/components/profile/WelcomeTypeformModal.tsx
src/db/migrations/0013_chilly_richard_fisk.sql
src/db/migrations/meta/0013_snapshot.json
src/db/migrations/meta/_journal.json
src/db/schema.ts
src/lib/token.test.ts
src/routers/user-router.ts
src/tests/helpers/user.helper.ts

iscekic · 2026-02-13T12:46:55Z

src/db/schema.ts

    is_bot: boolean().default(false).notNull(),
    default_model: text(),
    cohorts: jsonb().$type<Record<string, number>>().default({}).notNull(),
+    completed_welcome_form: boolean().default(false).notNull(),


Should we default to false? This way every user is going to see it, not just new users. 🤔

hmm, could be useful info but I'm guessing we don't want that for existing users @emilieschario?
if we don't we can just update the migration to set it true for existing users, what do you think?

ALTER TABLE "kilocode_users" ADD COLUMN "completed_welcome_form" boolean DEFAULT false NOT NULL; UPDATE "kilocode_users" SET "completed_welcome_form" = true;

let's make sure we only show to new users

I'll push the migration update to set that field to true for all existing users.

iscekic · 2026-02-13T12:47:54Z

src/components/profile/WelcomeTypeformModal.tsx

I think the bot may have a good point about theming

It's weird because dark mode on the modal wasn't triggering for me until I forced it in the browser console, regardless it should look good now

iscekic · 2026-02-13T12:48:09Z

src/components/profile/WelcomeTypeformModal.tsx

+        <Widget
+          id={WELCOME_FORM_ID}
+          style={{ width: '100%', height: '100%', minHeight: '400px' }}
+          className="my-form"


This class seems redundant?

iscekic · 2026-02-13T12:48:31Z

src/components/profile/WelcomeTypeformModal.tsx

+        onPointerDownOutside={e => e.preventDefault()}
+        onEscapeKeyDown={e => e.preventDefault()}
+      >
+        <DialogTitle className="sr-only">Welcome to the app</DialogTitle>


Suggested change

<DialogTitle className="sr-only">Welcome to the app</DialogTitle>

<DialogTitle className="sr-only">Welcome to Kilo</DialogTitle>

iscekic · 2026-02-13T12:49:04Z

src/components/profile/WelcomeTypeformModal.tsx

+        <DialogTitle className="sr-only">Welcome to the app</DialogTitle>
+        <Widget
+          id={WELCOME_FORM_ID}
+          style={{ width: '100%', height: '100%', minHeight: '400px' }}


Styles here and above are a bit weird, but I guess that's what we need to use because of the library?

it actually works fine without this.

kiloconnect · 2026-02-13T17:57:38Z

src/components/profile/WelcomeTypeformModal.tsx

+            email: userEmail,
+          }}
+          onSubmit={handleComplete}
+          onClose={handleSkip}


WARNING: Closing the Typeform widget also marks the welcome form as completed

Even if you later change the dialog behavior, onClose={handleSkip} currently calls the same completion mutation as submit. If the intent is to only persist completion on submit, consider removing this handler or changing it to record a distinct "dismissed" state.

kiloconnect · 2026-02-13T17:57:38Z

src/db/migrations/0012_square_marvel_apes.sql

@@ -0,0 +1,2 @@
+ALTER TABLE "kilocode_users" ADD COLUMN "completed_welcome_form" boolean DEFAULT false NOT NULL;
+UPDATE "kilocode_users" SET "completed_welcome_form" = true;


WARNING: Migration may mark users created during deploy as completed

UPDATE "kilocode_users" SET "completed_welcome_form" = true; will also affect any rows inserted after the ALTER TABLE but before the update runs (e.g. users signing up during the migration window), so they may not see the welcome modal even though they're "new". If that edge-case matters, a safer pattern is: add the column nullable/no default → backfill existing rows → then set NOT NULL + DEFAULT false.

This is such an edge case and the only fix (I believe) would be to add a timestamp to make sure we capture users created in-between. I'm okay with this current approach

…-survey

jfcsantos · 2026-02-16T11:58:56Z

@iscekic might giving this another look?

kiloconnect · 2026-02-16T12:00:27Z

src/db/migrations/0013_opposite_groot.sql

@@ -0,0 +1 @@
+ALTER TABLE "kilocode_users" ADD COLUMN "completed_welcome_form" boolean DEFAULT false NOT NULL;


WARNING: Migration defaults completed_welcome_form to false for all existing users

ALTER TABLE ... ADD COLUMN ... DEFAULT false NOT NULL will make every pre-existing row effectively have completed_welcome_form=false, so the modal will show for everyone until they close/submit it. If the intended behavior is “only new users see this”, the migration likely needs an explicit backfill for existing users (or a separate “dismissed_at/created_at cutoff” approach).

sorry @iscekic I lost the update on the merge conflict with main...fixing it now

jfcsantos added 8 commits February 13, 2026 10:24

Added a modal with a typeform survey that opens after User signup

faf42ba

hiding survey credits block

ffe3fbf

Merge branch 'main' into jsantos/profile-survey

c734a36

updated migrations

1b04c68

cleanup

ebabe3c

removing user_id

c30cb50

adding error handling and fixing migrations

aaca242

styling close button

5b7fab6

jfcsantos marked this pull request as ready for review February 13, 2026 12:33

kiloconnect bot reviewed Feb 13, 2026

View reviewed changes

iscekic reviewed Feb 13, 2026

View reviewed changes

styling and cleanup

cbab28d

jfcsantos requested a review from iscekic February 13, 2026 14:42

added update users to migration

fdff371

kiloconnect bot reviewed Feb 13, 2026

View reviewed changes

jfcsantos added 4 commits February 14, 2026 20:44

Merge branch 'main' of github.com:Kilo-Org/cloud into jsantos/profile…

18ac04b

…-survey

simplifying modal callbacks

f573bb8

Merge branch 'main' of github.com:Kilo-Org/cloud into jsantos/profile…

c75eff4

…-survey

recreating migrations

7793fda

kiloconnect bot reviewed Feb 16, 2026

View reviewed changes

fixing migration

c02fe9f

	<DialogTitle className="sr-only">Welcome to the app</DialogTitle>
	<DialogTitle className="sr-only">Welcome to Kilo</DialogTitle>

		@@ -0,0 +1,2 @@
		ALTER TABLE "kilocode_users" ADD COLUMN "completed_welcome_form" boolean DEFAULT false NOT NULL;
		UPDATE "kilocode_users" SET "completed_welcome_form" = true; No newline at end of file

		@@ -0,0 +1 @@
		ALTER TABLE "kilocode_users" ADD COLUMN "completed_welcome_form" boolean DEFAULT false NOT NULL; No newline at end of file

Conversation

jfcsantos commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Implementation Details

Uh oh!

kiloconnect bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

kiloconnect bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

kiloconnect bot commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Summary

Uh oh!

iscekic Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kiloconnect bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

kiloconnect bot Feb 13, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jfcsantos commented Feb 16, 2026

Uh oh!

kiloconnect bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

jfcsantos commented Feb 13, 2026 •

edited

Loading

kiloconnect bot commented Feb 13, 2026 •

edited

Loading

iscekic Feb 13, 2026 •

edited

Loading