Onboard your profile

CoSci works better when it knows your research context — your field, methods, and what you care about. On first run it seeds a starter profile so the cockpit isn’t empty; you can then ground it in your own work.

Seeded on first run

The one-click start.command seeds a profile automatically (this is what the ~1-minute first run is doing). In dev mode, the same thing happens via:

cd backend
uv run python seed_coscientist.py   # idempotent — safe to re-run

Ground it in your own work

CoSci can build a set of research profiles from a single file about you — for example a CV — so its questions, mechanisms and writing are grounded in your actual domain rather than a generic default. This turns the starter profile into your profile.

Point the onboarding at your file and CoSci drafts the profiles that shape how it collaborates with you across the lifecycle.

Reset

Your profile and all local state live in the SQLite database under backend/data/. To start clean:

rm backend/data/cockpit.db   # rebuildable; gitignored

Then re-run start.command (or seed_coscientist.py) to seed a fresh profile.