- Fewer sign-in interruptions. Viktor can use a saved authenticator key or check your own connected Gmail or Outlook for the site's verification code.
- Answer right in chat. If a code or phone approval still needs you, an inline card lets you respond without taking over the whole browser.
- Keep a way back in. Security keys, passkeys and unsupported verification screens still hand over to Viktor's Screen.
What's new
A verification code no longer has to turn a browser task into a manual takeover. When a site asks for a second factor, Viktor first tries the authenticator key saved with that login. If there isn't one, he can check your own connected Gmail or Outlook for the site's code.
If neither route finishes sign-in, a card in the conversation asks for your help. Enter the code there, or confirm that you approved the request on your phone.
How to use it
Ask Viktor to do a browser task as usual. For an authenticator-based login, you can add the authenticator key when saving the login on Viktor's Screen. Enrollment lets you check that the generated code matches your authenticator before saving.
Only the person who requested the task can answer its verification card. Codes and authenticator keys are kept out of the conversation and Viktor's model context.
Where it works
Automatic verification runs in Viktor's browser sessions. The inline card works on the web and desktop, with Slack also offering a code-entry flow. Passkeys, security keys and cases the automatic flow can't handle still use the screen takeover.


