1. Create Account
Sign up on beta, confirm your email, and wait for beta approval. Approval keeps the first beta small while we protect account privacy, support requests, and app stability.
Getting Started
This is the short path for new CO3 beta testers. We recommend starting here before reading every guide: create an account, wait for approval, choose model access, make simple V2 personas, start or continue a chat, and report what works or breaks.
2. Open The App
Once approved, use the app link to enter CO3. The app is where persona libraries, chat, model connection settings, language preference, feedback tools, and saved scenes live.
3. Connect Model Access
Some approved testers may have CO3-managed OpenAI, Gemini, or DeepSeek access. If not, you can bring your own provider key when the app lists a supported BYO option. Add or select model access only in the app's Connection Settings, and never send API keys through feedback or screenshots.
4. Make Personas
Character personas describe who the AI writes as. User personas describe who you write as. New cards should usually use the Version 2.0 template, but older Version 1.0 cards still work. Start with enough to chat, then add detail when something feels missing.
5. Start A Scene
Test normal replies, regenerations, empty-send continuation, out-of-character guidance, response feedback, and continuing a saved chat versus starting a separate new one. Longer scenes are especially useful for continuity and repetition testing.
6. Report Clearly
Use feedback for bugs, broken buttons, login trouble, mobile layout problems, model errors, repeated phrasing, archive likes that do not update, unexpected account state, and ideas that would make CO3 feel better.
First Login Checklist
- Confirm your email and wait for beta approval.
- Open the app and check whether integrated model access is available.
- If needed, add a BYO key in Connection Settings without sharing it anywhere else.
- Create or copy one simple Version 2.0 user persona and one simple Version 2.0 character persona.
- If Spanish is easier for you, set the site language from the app before testing labels and navigation.
- Start a short chat and try one normal reply, one regeneration, and one empty send.
- Flag one response issue with details, even if the issue is small.
- Check that saved personas and chats are still there after refreshing.
What To Notice First
- Can you find the app, help pages, feedback, and connection settings without guessing?
- Do page URLs and the browser back button behave the way you expect?
- Does the chat keep character voice, location, relationship context, and scene momentum?
- Does the selected user persona show as the Writing As persona you expected?
- Do public and private personas behave differently in a way that makes sense?
- Does mobile feel usable without buttons crowding the screen, menus getting clipped, or important paths hiding behind too much detail?
- Do error messages tell you what happened and what to do next?
New Tester Shortcut
If you are helping with a first beta pass, use the tester script instead of trying to explore every page at once. It gives you a short route through account setup, app access, personas, chat, feedback, and saved work.