In development
From a first sign-in to a conversation with room to grow
Kenzai’s development work traces a connected journey: start an account without linking Gmail, preserve setup progress, and carry a conversation from beside the task board into a larger workspace. These updates span October 13, 21, and 22, 2026. They are development updates, not verified customer availability.
October 13, 2026: A conversation beside the task board
The story begins beside the work itself, with a place to ask a question while the task board remains in view.
Development adds an agent chat sidebar that docks beside the task board on wide screens and slides in from the right on smaller screens.
It includes suggested prompts, a new-chat button, and keyboard controls: Enter to send and Shift+Enter for a new line.
October 13, 2026: More room, without losing the draft
When a conversation needs more space, the development direction is continuity rather than a restart.
Kenzai is developing a full-page agent chat interface that keeps the current conversation and unsent drafts intact when switching workspace views.
A separate New chat action starts a fresh session.
This remains a draft release candidate, not a production launch.
October 21, 2026: Carrying the conversation into Work
The next step extends that continuity to the move from the sidebar into Work.
A development improvement carries the same conversation from the sidebar into Work.
This development work keeps drafts, attachments, audience and model choices, and pending actions intact.
Production availability is not established.
October 22, 2026: Account access, separate from Gmail linking
Before a conversation begins, there is the first step into an account. Kenzai’s development work separates that step from the choice to link Gmail.
Development work adds identity-only Google login and signup, separating account access from optional Gmail linking.
Live Google sign-in and onboarding acceptance are still pending.
October 22, 2026: Setup progress that stays with the account
That account-first direction also shapes setup: completing or skipping it should remain meaningful when a user returns.
Development work restores authenticated account setup for accounts without stored connections.
Finishing or skipping setup preserves each user’s completion state across reloads and retries, while keeping other users’ data unchanged.
Deployed onboarding remains unverified. These are development updates, not verified customer availability.
