What's new.
What you can do in Kvendra now that you couldn't before — newest first — and the milestones we have reached along the way.
News
- Better protection for your account. Two-step verification with an authenticator app, email alerts if your verification method or email changes, and 1-hour sessions that renew on their own in the dashboard, Claude Code and the CLI. If you sign in with GitHub, we only accept accounts with two-factor authentication turned on in GitHub. From October 14, two-step verification is required to sign in with email and password. See how to set it up.
- Share your project without oversharing. Publish a snapshot of your project, with its overview and manual, for whoever you choose: an unlisted link, your organization, or organizations linked to yours through an invite code. You can include PDFs, images, video and audio (we keep a copy with the metadata removed, scan PDF text for sensitive data, and ask you to confirm images, video and audio before they go out), and files are checked for malware before anyone can open them; if a file can't be checked, it isn't shared. If the author allows it, recipients can fork it into their own project: it arrives as a copy for review and nothing is activated without their approval.
- Teams with real roles. Each member works with their role's permissions, from Claude Code too: viewers only read, and members propose changes to key items for an owner or admin to approve. Invitees accept or decline from their own account, admins can choose their username, and storage and search quotas are shared across the team. Team is open by waitlist: join it.
- Smoother Claude Code and CLI. The CLI renews your session on its own and no longer asks for
kvendra loginevery time it expires (update to the latest version). In Claude Code, the consulting assistant is now called/kvendra. Each component's manual includes screenshots, PDFs and videos, and test evidence is saved as project files. Script keys are now called "Access tokens" (Pro). - Private data that stays private. Internal accounts, emails and addresses are stored as references and only people with permission see their value; you manage them from an editor in the dashboard. What only makes sense on your machine stays on your machine, encrypted by the CLI. And anything you import from others is marked as external content, so your agents treat it as information, never as instructions.
- Your files next to your knowledge. Upload screenshots, reports and specs to your workspace and link them to what you document: 5 GiB on Pro and 10 GiB per seat on Team. Export all your knowledge as a single file whenever you want. And if you cancel Pro, we keep your workspace for 6 months in case you come back; after that, your knowledge, files, backups and login are deleted for good.
Evolution
- Kvendra Pro is live
The hosted knowledge base, the dashboard and subscriptions. Where this timeline starts.
- Team workspaces
Invite members, manage seats, and let invitees accept or decline from their own account. Team is open by waitlist: join it.
- Roles that also apply in Claude Code
Each member works with the permissions of their role, wherever they connect from.
- Workspace files and full export
Files next to your knowledge, one-file export and quotas shared across the team.
- Publications
Share a snapshot of a project, with its overview and manual, through an unlisted link.
- Publications with files, for your organization
PDFs, images, video and audio in a publication, and audiences limited to your organization.
- Linked organizations
Share publications with organizations linked to yours through an invite code.
- Private values and two-step verification
An editor for private values, local values that stay on your machine, and authenticator-app verification.
- Proposals, forks and self-renewing sessions
Members propose changes for approval, publications can be forked for review, and sessions renew on their own.
Release notes
Technical notes for every version live with each project.