App Stability
Account approval, app login, private personas, saved chats, model connection settings, public persona copies, public archive likes, and logout/login behavior.
Beta Status
CO3 is in controlled beta testing right now. Use this page when you want the current testing focus: what is active, what to try first, and what feedback helps most.
Current State
- Access is approval-based. New accounts can sign in, but app features unlock after beta approval.
- Model access is controlled. Some testers may receive CO3-managed OpenAI/Gemini access; everyone can still use their own provider key if needed.
- Private and public persona tools are active. Character personas and user personas can be created, edited, duplicated, liked, sorted, and tested.
- Reports are being reviewed. Feedback, bugs, response flags, persona reports, and model-health issues all reach CO3 review tools.
Test These First
- Create an account, confirm the email, and wait for approval.
- Log in on beta, enter the app, and confirm the account stays connected after reload.
- Open Connection Settings in the app and choose CO3-managed access if granted, or add a BYO Gemini/OpenAI key.
- Create or copy one simple user persona and one simple character persona.
- Start a chat, regenerate once, try one empty send, and try one OOC note in double parentheses.
- Flag one response with typed details, even if the issue is small.
- If a chat has the wrong Writing As persona or mishandles time passing, report that too.
- Try mobile navigation or mobile chat if you are testing from a phone.
Chat Quality
Repetition, wrong point of view, ignored steering, stale scene location, blandness, overexplained reactions, identity drift, and OOC instructions that do not stick.
Mobile And UI
Cramped buttons, cut-off menus, keyboard weirdness, confusing labels, missing links, unreadable text, or anything that makes the app hard to use on a phone. Current mobile work is focused on clearer hierarchy, not removing CO3's deeper tools.
Known Watch Areas
- OOC guidance should affect later replies without the character treating it as spoken dialogue.
- Regenerated replies should take a meaningfully different route, not lightly paraphrase the first version.
- Characters should not cling to a question after the user dodges, jokes, redirects, or changes the scene.
- Characters should not constantly open with stock phrases or repeat the user's wording as a processing beat.
- Character reactions should not explain every user action back as a visible cause-and-effect body-language receipt.
- Persona creation should feel approachable even when the full card has many optional fields.
Before Reporting
- Include the page or app area where the issue happened.
- Include what you clicked or typed before the problem appeared.
- Include your browser and device when the issue looks visual or mobile-specific.
- Do not send passwords, API keys, tokens, or billing information.
Browser Scope
Controlled beta testing is currently focused on mobile Safari, mobile Chrome, desktop Chrome, and common desktop browsers. If something fails somewhere else, it is still useful to report, but these browsers are the first places CO3 is trying to make reliable.