Troubleshooting

Start 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.

Kin’s failure message includes recovery guidance when available. Follow its named wait or account action before repeating the request. If Space says a session ended before its background work settled, saved history remains available: inspect that history and the affected files before starting more work. Ending without settlement does not establish that the work completed. A session that reached its time limit or was closed for an update says so. If the notice says a command is still running, inspect it before starting another.

If Kin says what you sent is more than her model can read at once, send it in smaller parts or use /rewind to take it back. If the whole conversation is too long, send /compact or start a new session. An answer cut off at the model’s output limit, or a turn at its limit of model rounds, needs a request to continue. Repeating the same oversized input will not make room.

If a model or history list could not be read, follow its failure message and retry; a failed read does not mean the list is empty.

Messages about a conversation stand just above its message box; a failed turn is explained once in that conversation, and a passing note there lasts about eight seconds. Most other results stay beside the control that caused them. What still needs a notice stands below the bar, clear of open panels, as one compact note; N more opens the others and Show less folds them. Requests come first, then failures, then information. Information leaves after about four seconds and a request note after about six, paused only while your pointer or keyboard focus is on that note; the request itself still waits in its session. Failure notices stay until dismissed or until the problem clears.

Notices say what happened in words. A failure is titled with what could not be done, stays with the part of the page that needs attention and offers Try again where the same check can run again. An empty list explains what belongs there; an unavailable action explains what needs to be settled first. In a menu, you can still focus that action to read its reason.

Space will not open

At the front door, kinra.space:

• There is no Space for this account: the Kinra account you signed in with holds no Space. Check that you used the account your Space was set up for, or ask the person who invited you.
• Your Space is paused: your Space is suspended until the person who looks after it resumes it. Ask the person who invited you.
• Your Space is not ready yet: choose Try again in a few minutes.
• This sign-in has expired, Pocket ID is not answering right now or another sign-in message: choose the page’s button to start again from the front door.

At your Space’s own address:

• Come inside appears: sign in with the Kinra account your Space belongs to.
• This Space belongs to a different account: the Kinra account you signed in with does not own the Space at this address. Open the front door, which takes you to the Space your account holds, or sign in to Pocket ID with the account your Space was set up for.
• This Space is paused or This Space is not ready yet: as at the front door, ask the person who invited you or try again in a few minutes.
• This Space is not answering right now: try again in a moment. If it persists, ask the operator to check the machine and application.
• There is no Space at this address: check the address you opened. Go to Kinra Space opens the front door, which takes you to yours.
• Your Space could not be reached: check your connection and choose Try again. If it persists, ask the operator to check the machine and application.
• Your Space is being prepared: the entrance checks again on its own while setup runs; Check now checks at once. Report a persistent failure.
• Your Space is still there: this device is offline. Restore connectivity, then choose Try again. 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

1. Check for Reconnecting beside the message box and on the session’s row in the sidebar. Wait for the connection to return before retrying a message.
2. Look for a question, workspace trust decision, approval, or Git access review in the conversation area where the message box usually sits. A folded request has Show. One asked in Kin’s panel waits until you show the panel again; the panel and page can each have a request waiting.
3. If the message box says Watching this session., another window or device has the keyboard. Returning to use the page takes a free keyboard automatically. If another device still holds it, choose Take the keyboard to write here.
4. Check Connections for model readiness and the composer for the selected model. Complete any pending provider sign-in. If Kinra says your Space is suspended, see the Kinra connection.

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 under Live in the sidebar; ended work appears in Session history…. The history control beside Live searches across workspaces. Continue an existing session instead of creating a new one when you need its earlier context.

Your personal conversation is in Kin’s workspace, named Chat in Live. Chat and Show Kin take up the same conversation. It has no separate workspace row. Finished means a live turn ended while you were elsewhere; opening the session clears that state, and its saved messages remain available.

Transient reasoning is not replayed in saved history. Its absence is different from missing conversation messages.

A message draft seems to be missing

Return to the session where you wrote it: each session keeps its own unsent words and attachments, even when several sessions share a workspace. Starting another session does not bring that draft with it. A New session with words or attached files stays under Live when you switch away; choose that row to continue. An entirely empty new session ends when you leave it.

See Conversations for starting and returning to sessions.

Your home looks different

• Cards you had are gone. Kin keeps your home now. An earlier board you had never changed opens with the Sessions card alone, and a card you removed stays off. Choose Ask Kin on Home for the cards you want. See Your home.
• Your home could not be read. Choose Try again. A home already shown keeps its cards when a later read fails or finds the arrangement file half written.
• This card isn’t available. The card is of a kind this Space does not know. Choose its K to ask Kin what it was meant to be, rebuild it or take it away. Sessions stays on Home.
• Kin cannot start a fresh conversation. Finish a message awaiting acceptance, or send or remove files attached in another workspace, then try Ask Kin again. Your words are kept while the notice explains the reason.
• A home file still refers to spren or .space. Current home files live under ~/Workspace/Kin. The move keeps the old .space files, but changes there no longer update Home. Ask Kin to update instructions or scripts that still name those earlier paths.

A preview is blank or cannot open

Choose Preview not displaying? for guidance or Try again for a fresh preview. On an app’s App view or a page, they appear only once it is slow to load or has failed. For a file, View source or File details leaves the preview, and Download original gets the saved file rather than an unsaved edit. A long wait or an unsuccessful load check does not mean the file is corrupt. See preview recovery, including browser PDF support and the Apple app’s download limitation.

A file will not save or upload

• Changed elsewhere: inspect the newer version and choose Use the newer text or Keep mine. Undo restores the words replaced by Use the newer text until the text next changes; in Files those words become an unsaved draft. 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 MB; a message can attach at most eight files.
• Draft too large or not plain text: Files saves text files up to 1 MB and refuses a draft holding a character a text file cannot keep. The draft stays; shorten it, or remove the character, then save again.
• A rename or move is refused: read the reason at the foot of the tree. A name already there is never replaced; choose another name, or move or rename the existing one first. A workspace’s own folder, a repository’s .git and a project’s copies cannot be moved from Files.
• Go to file does not list a file: check its name, and choose Show hidden files for one whose name starts with a dot. Go to file leaves out a project’s copies, Git’s folder, the Trash and folders that tools fill, such as node_modules, dist and build, and in a very large workspace it reads only part and says so. Open the file’s folder in the tree instead.

For Notes, choose Stay when leaving would lose unsaved work. Each of its files’ configured folder must already exist. See Files.

Source needs attention

Try again retries a failed read; Refresh Source reads the current repository. A failed Keep, Push, Pull or Check GitHub reports under the places. Read the notice and Git output, settle its reason, then repeat that move. Keeping a checkpoint waits while files are in conflict; no remote means there is nowhere to check or push to. If the lines of work can’t be read, the map says so with its own Try again. A read that takes longer than twenty seconds stops and says so; choose Refresh Source to try again. After a failed refresh, it labels the last successful map, and Push and Pull wait until Source can read the current comparison. Keep and Check GitHub remain available where their own conditions allow them. See Source for the moves and how to recover from a joining that stopped partway.

An incomplete change list does not establish that the repository has no changes. Choose Refresh Source to read it again. If the warning remains, review all changes in the Terminal, or ask Kin to inspect the repository, before relying on the list or keeping a checkpoint. Unread checkpoint counts and comparisons with GitHub also stay unknown. If the warning remains, use the Terminal or ask Kin to inspect that part.

Source reads files without running the project’s conversion programs. A project that stores converted files can therefore show a file as changed even when its normal Git commands would consider it unchanged. Inspect that file in the Terminal before keeping a checkpoint; keeping uses the project’s normal Git settings.

A new workspace stopped

Use Resume workspace → Try this workspace again for a retained workspace. For a portfolio, choose Resume portfolio…, then Try the failed ones again when its folder is ready, or Try this portfolio again when it is not. Resolve the reported connection or destination problem first. Keep any partial clone files; do not delete them merely to make setup retry.

A shell, view, or custom card disconnected

• Terminal: use Rejoin shell. Inspect output and files before rerunning a command; it may have completed while the browser was away. If the page says it could not be opened on this workspace, two of your terminals have the same name: open the machine’s Terminal, rename one, and try again. If it says more was typed before it was ready than it holds, none of that was sent: rejoin, then type or paste it again.
• Running view: check that its application is still running and its files still exist. If Enable private view appears, choose it and follow the new window. Allow pop-ups for your Space if the window is blocked, then try again; open an expired view again from Space.
• Custom card: use Reload after nested asset changes. If the card says This card’s files are gone, check its folder or choose its K to ask Kin to rebuild it or take the card away.
• Copy or Share unavailable: select and copy normally, or download the original file. Device permissions and browser support affect these controls.

Something on a phone does not behave

• Pulling in from the edge does nothing. The drawer’s edge gesture belongs to the installed app. In a browser tab that movement is the browser’s own Back, and Space leaves it alone. Use the menu control in the topbar, or install Space from Devices and installation.
• The drawer will not close by dragging. A drag that starts on the terminal, on a table or code block that scrolls sideways, on the folder trail, or on text you have selected belongs to that thing. Tap the dimmed page or press Escape.
• Kin’s sheet does not go away when pulled. Pull from its grip or the bar at its top; a pull that starts in the conversation scrolls it instead. Hide Kin always puts it away.
• Kin or the terminal looks stuck after the Space app was in the background. Bring the Space app forward and wait a moment: Space reconnects as soon as it is visible, and replaces a connection that only looks alive. If the terminal still says it is disconnected, choose Rejoin shell.
• Empty space sits under the composer, or the status bar is hard to read. Your Home Screen icon was added before Space’s status bar became solid, and iOS keeps the status bar an app had when it was added. Remove Space from the Home Screen, then add it again from Safari with Share → Add to Home Screen. The new icon takes Safari’s sign-in, and your drafts and settings stay in your Space.
• Copying from the terminal does nothing. Use Select in the key row to turn the visible rows into selectable text, then copy with your device’s own handles. If the terminal offered a selection and the browser refused it, Copy selection appears in the topbar; one tap takes it.

A machine check failed

Open Your machine and choose Ask Kin to look beside the failed check. It prepares a request in the Home workspace; review the draft and send it. For a manual check, expand Read its log yourself (or Read the logs yourself), choose Open Terminal and run the displayed command. The failure stays until that check runs again and passes. Give the person who looks after your Space the visible result if it persists.

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. No public support service is announced. Public signup is not open; use the contact that provided your Space.