Kinra Space / Reference and help
Troubleshooting
Find the next useful check when sign-in, a conversation, a file, or a saved project needs attention.
Experimental · private access. Public signup is not open.
Read as MarkdownStart with the message beside the affected control. Keep unsaved text before reloading. A failed reply does not establish whether an operation changed files or an external service.
Space will not open
- Come inside appears: sign in with the identity appointed for this Space.
- The home cannot be reached: check your connection and retry. If it persists, ask the operator to check the machine and application.
- Setup is unfinished: the entrance checks again while setup runs. Follow any offered account-setup action; report a persistent failure.
- Offline reconnect page: restore connectivity, then reopen Space. Private history and files are loaded from the machine after authentication.
Installing another app icon or repeatedly creating sign-ins cannot repair an unreachable machine.
Kin does not answer
- Check for Reconnecting above the conversation. Wait for the connection to return before retrying a message.
- Look for a question, workspace trust decision, approval, or Git access review in that session.
- If watching another client’s session, have its current writer release the keyboard before choosing Take the keyboard.
- Check Your profile for model readiness and the composer for the selected model. Complete any pending provider sign-in.
After a palette submission, wait for acknowledgement. A second question sent during that wait is refused and is not kept. If model setup fails, check your draft for the restored question.
A session seems to be missing
Check that you have the right workspace. Live work appears in the sidebar; ended work appears in History. The Workspaces history control searches across workspaces. Continue an existing session instead of creating a new one when you need its earlier context.
Transient reasoning is not replayed in saved history. Its absence is different from missing conversation messages.
A file will not save or upload
- Changed elsewhere: inspect the newer version and choose Use the newer text or Keep mine. Keep a separate copy of important competing edits.
- Removed behind the editor: Save it again can recreate it.
- Still unsaved after saving: newer typing may have occurred during the request; save again when it finishes.
- Permission error: inspect the named path and workspace. Ask for help with that file’s permissions rather than changing the whole machine’s access.
- Upload name conflict: rename the incoming file or deliberately resolve the existing one. Uploads do not overwrite files.
- Upload too large: each file is limited to 64 MiB; a message can attach at most eight files.
For Scratchpad, choose Stay when leaving would lose unsaved work. Its configured folder must already exist. See Files.
A project or Depot operation stopped
Use Resume project or Resume portfolio… → Retry failed for retained setup. Resolve the reported connection or destination problem first.
In Depot Source, Retry saved operation recovers the retained request. If Inspect outcome appears, compare its completed steps and current facts before taking another action. For a saved-file view that closes, check the Kinra connection and Depot access before reopening it.
A disabled merge needs Depot’s current approval for the inspected revisions. A comment or approval of an older revision does not satisfy that requirement. See Saving with Depot.
A shell, preview, or widget disconnected
- Terminal: use Rejoin shell. Inspect output and files before rerunning a command; it may have completed while the browser was away.
- Running artifact: check that its application is still running and its files still exist.
- Custom widget: use Reload after nested asset changes. Check its files if the tile reports them missing.
- Copy or Share unavailable: select and copy normally, or download the original file. Device permissions and browser support affect these controls.
Give the operator a useful report
Include the page and workspace, the action you took, what you expected, the exact visible error, and the approximate time with time zone. Your machine shows the Space revision when reachable. Say whether reconnecting changed the result and whether you still have unsaved work.
Include a screenshot only after checking it for private text, filenames, account details, and sign-in codes. Never send passkeys, tokens, credentials, or private preview links. There is no public support or signup service announced for this experimental product; use the contact that provided your Space.