Workspace access
Use your account email and password.
Ask your workspace administrator for a fresh invitation if you need to recover access.
Start with a question, an idea, or something you’re working on.
AI can make mistakes. Review important output.
Set or reset your Studio email and password using the workspace key. Saving these credentials ends existing browser sessions.
Open local projects, ask questions about selected files and review diffs in Klyrn Studio for Windows.
In VS Code, use Install from VSIX, then choose Klyrn: Connect from the Command Palette.
Extract Klyrn CLI and add it to your PATH, or run it from the extracted folder. On Windows PowerShell, use .\klyrn.exe from that folder.
.\klyrn.exe
klyrn login klyrn models klyrn ask -f main.go "Explain this file"
klyrn login
Pair Windows Studio or the CLI with one project. Each token can open, start, and continue conversations in that project for 30 days.
Create a project to pair a device.
In the terminal, run klyrn project chats to list conversations or klyrn project chat to start one.
klyrn project chats
klyrn project chat
Use your device or password manager to sign in. Enter the workspace key to add or remove a passkey.
No saved passkeys.
Checking RunPod connection…
Sends one fixed test prompt. It can start a billable worker, counts toward your Studio RunPod cap, and may take up to 12 minutes.
RunPod handles prompts and selected files only when you choose the RunPod route. Usage is billed to your RunPod account.
Set 0 for unlimited requests through Studio. RunPod reports billing in your RunPod account.
Create a copy from a Studio JSON export. Studio gives conflicting project names an import suffix.
Select files for the next reply or choose up to four for an edit.
To test the proposal, unpack the candidate into a disposable local copy of your project.
Copy the messages through this reply into a new conversation. Attach files to the branch as needed.
HTML, CSS, and built-in browser controls