# Admin Console
Source: https://docs.kisuke.dev/advanced/admin-console

Manage your devices and account at auth.kisuke.app

## Overview

The Kisuke Admin Console is available at [auth.kisuke.app/login](https://auth.kisuke.app/login). It gives you a web interface to manage your devices, auth keys, and account settings.

## Accessing the Console

Navigate to [auth.kisuke.app/login](https://auth.kisuke.app/login) and sign in with the same account you use in the Kisuke app.

## What You Can Do

* **View all devices** — See every machine registered to your account with online/offline status
* **Manage access** — Control which devices can connect to each other
* **View connection info** — Check last seen times and connection types
* **Remove devices** — Revoke access from old or lost devices


# Overview
Source: https://docs.kisuke.dev/concepts/kisuke-connect



Kisuke Connect is a lightweight service that runs on your desktop or server and acts as the bridge between your machine and the Kisuke app. It exposes your terminal, files, and editor over an end-to-end encrypted connection — letting you access your development environment from anywhere.

<Info>
  New to Kisuke? Follow the [Quickstart](/quickstart) to get everything set up in minutes.
</Info>

## How It Works

```mermaid actions={false} theme={null}
graph LR
  Client["Kisuke App"] <-->|Encrypted| Laptop["Kisuke Connect"]
  Laptop <-->|Encrypted| Server["Kisuke Connect (Server)"]
  Server <-->|Encrypted| Client
```

Kisuke Connect maintains a persistent encrypted tunnel between your devices. When you open a terminal, edit a file, or browse the web through Kisuke, the traffic flows through this tunnel — routed via Kisuke's global relay network for reliable connectivity from any network.

## Key Benefits

### Zero Configuration

Just sign in on both devices and they find each other automatically. Kisuke Connect handles:

* NAT traversal
* Firewall penetration
* DNS resolution
* Key exchange

### End-to-End Encrypted

All traffic between your devices is end-to-end encrypted — relay servers and coordination servers never see your data. Kisuke uses the **Noise Protocol Framework** for its secure tunnels, the same cryptographic foundation that WireGuard is built on:

* **Noise Protocol** for authenticated key exchange and session establishment
* **X25519** key exchange
* **ChaCha20-Poly1305** encryption

### Global Relay Network

All traffic routes through Kisuke's relay network spanning **14+ regions worldwide** — keeping latency low regardless of where you are.

```mermaid actions={false} theme={null}
graph LR
  Client["Kisuke"] <-->|Encrypted| Relay["Kisuke Relay"] <-->|Encrypted| Host["Kisuke Connect"]
```

<Note>
  Relay servers cannot decrypt your traffic. Everything is end-to-end encrypted — relay servers only forward encrypted packets.
</Note>

### Works Anywhere

Kisuke Connect works through:

* Home networks
* Corporate firewalls
* Mobile data (LTE/5G)
* Coffee shop WiFi
* Hotel networks
* Carrier-grade NAT

## Use Cases

### Remote Development

Access your development machine from anywhere. Run builds, execute tests, and use terminals on your powerful desktop — all from your phone on the train.

### Server Access

Connect to servers in your home lab, cloud VMs, or office machines without exposing ports to the internet. No bastion hosts. Just connect via Kisuke Connect.

### Multi-Device Workflow

Work seamlessly across devices:

* Start a build on your laptop
* Check progress from your phone
* Fix a bug from your tablet
* All connected, all the time

## Next Steps

<CardGroup>
  <Card title="The Relay System" icon="arrows-rotate" href="/concepts/relay-system">
    Learn about relay servers and NAT traversal.
  </Card>

  <Card title="Security" icon="shield" href="/concepts/security">
    Understand Kisuke's security model.
  </Card>
</CardGroup>


# The Relay System
Source: https://docs.kisuke.dev/concepts/relay-system

How Kisuke relay servers connect your devices

## Overview

All traffic between your Kisuke devices routes through Kisuke's relay network — a global network of encrypted relay servers (DERP — Designated Encrypted Relay for Packets). This ensures connectivity regardless of your network environment, without any port forwarding, firewall rules, or VPN configuration.

## How Relays Work

```mermaid actions={false} theme={null}
graph TD
  A["Kisuke App"] -->|Encrypted| Relay["Kisuke Relay"]
  B["Kisuke Connect"] -->|Encrypted| Relay
```

## Relay Network

Kisuke operates relay servers across **14+ regions worldwide**. Your devices automatically connect to the nearest relay for the lowest possible latency.

## Performance

### Relayed Connection

* Latency: +10-50ms depending on relay distance
* Bandwidth: Limited only by your internet connection

## Monitoring

Check your connection status in the Kisuke app:

1. Go to **Connect** > **Devices**
2. Tap on a connected device
3. View connection details

## Next Steps

<CardGroup>
  <Card title="Security" icon="shield" href="/concepts/security">
    Learn about encryption and security.
  </Card>
</CardGroup>


# Security & Encryption
Source: https://docs.kisuke.dev/concepts/security

How Kisuke keeps your data secure

## Overview

Security is fundamental to Kisuke. All communications between your devices are encrypted end-to-end, and we follow industry best practices to protect your data.

## End-to-End Encryption

All traffic between your devices is encrypted using modern cryptographic protocols:

* **Key Exchange** - X25519 elliptic curve Diffie-Hellman
* **Encryption** - ChaCha20-Poly1305 AEAD
* **Authentication** - Ed25519 signatures

```mermaid actions={false} theme={null}
graph LR
  A["Device A"] <-->|"E2E Encrypted"| B["Device B"]
```

## Zero Trust Architecture

Kisuke operates on zero-trust principles:

* **No implicit trust** - Every connection is verified
* **Device verification** - Each device has a unique cryptographic identity
* **Account binding** - Devices are bound to your authenticated account

## Authentication

Kisuke supports authentication through trusted identity providers:

* **Claude** (Anthropic)
* **Google**
* **OpenAI**

This means:

* No passwords to manage for Kisuke
* Leverage existing security (2FA, etc.) from your provider
* Single sign-on across all your devices

## Data Handling

### What Kisuke Stores

* Device identities and public keys
* Connection metadata (for routing)
* Account associations

### What Kisuke NEVER Stores

* Your code or files
* Terminal commands or output
* AI conversation content
* Any decrypted traffic

<Note>
  Your data flows directly between your devices. Kisuke servers only facilitate connections—they never see your actual data.
</Note>

## Network Security

### Firewall Recommendations

Kisuke Connect works through most firewalls with no configuration needed. For optimal performance, allow outbound TCP on port 443.

### How Traffic Flows

All traffic routes through Kisuke's encrypted relay network. Relay servers only forward encrypted packets — they cannot decrypt your traffic.

Relay servers **only see**:

* Encrypted blobs
* Which device to forward packets to

Relay servers **cannot see**:

* Your terminal commands
* Your code
* Your files
* Anything meaningful about your traffic

## Security Reporting

Found a security vulnerability? Please report it responsibly:

* Email: [security@kisuke.app](mailto:security@kisuke.app)
* Do not disclose publicly until addressed


# Web Browser
Source: https://docs.kisuke.dev/features/browser

Built-in browser with developer tools for testing and debugging

## Overview

Kisuke includes a built-in web browser with developer tools for testing and debugging your web projects. Preview applications, inspect network requests, and test APIs — from any device.

## Features

### In-App Preview

Preview your web applications without leaving Kisuke:

* Local development servers
* Remote URLs
* Static files

### Developer Tools

Basic developer tools for debugging:

* View source
* Console output
* Network requests
* Element inspection

### Integration

The browser integrates with other Kisuke features:

* Open URLs from terminal output
* Preview from file editor
* Share context to AI chat

## Use Cases

### Local Development

When running a dev server on your connected machine:

1. Start your dev server in terminal (`npm run dev`)
2. Note the URL (e.g., `http://localhost:3000`)
3. Open Browser in Kisuke
4. Enter the URL

Kisuke Connect routes the traffic through your secure tunnel automatically.

### Documentation

Keep documentation open while coding:

* API references
* Framework docs
* Stack Overflow answers

### Testing

Quick testing of web applications:

* Check responsive design
* Test user flows
* Verify API responses

## Navigation

### Address Bar

Tap the address bar to:

* Enter URLs
* Search (uses your default search engine)
* Access recent history

### Controls

* **Back/Forward** - Navigate history
* **Refresh** - Reload the page
* **Share** - Share URL or send to chat

## Accessing Local Servers

When connected to a computer running a local server:

```bash theme={null}
# On your computer
npm run dev
# Server running at http://localhost:3000
```

In Kisuke browser, navigate to:

* `http://localhost:3000` - Works through Kisuke Connect

Kisuke automatically routes localhost URLs to your connected device.

## Limitations

The built-in browser is designed for development preview, not general browsing:

* Limited extension support
* Simplified dev tools
* Focus on development use cases

For full browsing, use your device's native browser.


# Coding with AI
Source: https://docs.kisuke.dev/features/coding-with-ai

AI-powered coding assistant integrated into Kisuke

## Overview

Kisuke includes an integrated AI coding assistant. Get debugging help, code generation, and documentation without leaving the app — from any device. Connect your own account from any supported provider.

Kisuke is **provider agnostic** — all skills, slash commands, and features work across Anthropic, OpenAI, Google, and every other supported provider.

## Getting Started

1. Open Kisuke
2. Tap **Chat**
3. Sign in with your AI provider
4. Start coding with AI

## Supported Providers

### Official (First-Party)

<CardGroup>
  <Card title="Anthropic" icon={<svg viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><path fill="currentColor" d="M17.3041 3.541h-3.6718l6.696 16.918H24Zm-10.6082 0L0 20.459h3.7442l1.3693-3.5527h7.0052l1.3693 3.5528h3.7442L10.5363 3.5409Zm-.3712 10.2232 2.2914-5.9456 2.2914 5.9456Z"/></svg>}>
    Claude models — OAuth or API key
  </Card>

  <Card title="OpenAI" icon={<svg viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg"><path fill="currentColor" d="M14.949 6.547a3.94 3.94 0 0 0-.348-3.273 4.11 4.11 0 0 0-4.4-1.934A4.1 4.1 0 0 0 8.423.2 4.15 4.15 0 0 0 6.305.086a4.1 4.1 0 0 0-1.891.948 4.04 4.04 0 0 0-1.158 1.753 4.1 4.1 0 0 0-1.563.679A4 4 0 0 0 .554 4.72a3.99 3.99 0 0 0 .502 4.731 3.94 3.94 0 0 0 .346 3.274 4.11 4.11 0 0 0 4.402 1.933c.382.425.852.764 1.377.995.526.231 1.095.35 1.67.346 1.78.002 3.358-1.132 3.901-2.804a4.1 4.1 0 0 0 1.563-.68 4 4 0 0 0 1.14-1.253 3.99 3.99 0 0 0-.506-4.716m-6.097 8.406a3.05 3.05 0 0 1-1.945-.694l.096-.054 3.23-1.838a.53.53 0 0 0 .265-.455v-4.49l1.366.778q.02.011.025.035v3.722c-.003 1.653-1.361 2.992-3.037 2.996m-6.53-2.75a2.95 2.95 0 0 1-.36-2.01l.095.057L5.29 12.09a.53.53 0 0 0 .527 0l3.949-2.246v1.555a.05.05 0 0 1-.022.041L6.473 13.3c-1.454.826-3.311.335-4.15-1.098m-.85-6.94A3.02 3.02 0 0 1 3.07 3.949v3.785a.51.51 0 0 0 .262.451l3.93 2.237-1.366.779a.05.05 0 0 1-.048 0L2.585 9.342a2.98 2.98 0 0 1-1.113-4.094zm11.216 2.571L8.747 5.576l1.362-.776a.05.05 0 0 1 .048 0l3.265 1.86a3 3 0 0 1 1.173 1.207 2.96 2.96 0 0 1-.27 3.2 3.05 3.05 0 0 1-1.36.997V8.279a.52.52 0 0 0-.276-.445m1.36-2.015-.097-.057-3.226-1.855a.53.53 0 0 0-.53 0L6.249 6.153V4.598a.04.04 0 0 1 .019-.04L9.533 2.7a3.07 3.07 0 0 1 3.257.139c.474.325.843.778 1.066 1.303.223.526.289 1.103.191 1.664zM5.503 8.575 4.139 7.8a.05.05 0 0 1-.026-.037V4.049c0-.57.166-1.127.476-1.607s.752-.864 1.275-1.105a3.08 3.08 0 0 1 3.234.41l-.096.054-3.23 1.838a.53.53 0 0 0-.265.455zm.742-1.577 1.758-1 1.762 1v2l-1.755 1-1.762-1z"/></svg>}>
    GPT models — OAuth or API key
  </Card>

  <Card title="Google" icon={<svg viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg"><path fill="currentColor" d="M15.545 6.558a9.4 9.4 0 0 1 .139 1.626c0 2.434-.87 4.492-2.384 5.885h.002C11.978 15.292 10.158 16 8 16A8 8 0 1 1 8 0a7.7 7.7 0 0 1 5.352 2.082l-2.284 2.284A4.35 4.35 0 0 0 8 3.166c-2.087 0-3.86 1.408-4.492 3.304a4.8 4.8 0 0 0 0 3.063h.003c.635 1.893 2.405 3.301 4.492 3.301 1.078 0 2.004-.276 2.722-.764h-.003a3.7 3.7 0 0 0 1.599-2.431H8v-3.08z"/></svg>}>
    Gemini models — OAuth or API key
  </Card>

  <Card title="xAI" icon={<svg viewBox="0 0 727.27 778.68" xmlns="http://www.w3.org/2000/svg"><polygon fill="currentColor" transform="translate(-134,-113.32)" points="508.67 574.07 761.27 213.32 639.19 213.32 447.64 486.9"/><polygon fill="currentColor" transform="translate(-134,-113.32)" points="356.08 792 417.12 704.83 356.08 617.66 234 792"/><polygon fill="currentColor" transform="translate(-134,-113.32)" points="508.67 792 630.75 792 356.08 399.72 234 399.72"/><polygon fill="currentColor" transform="translate(-134,-113.32)" points="761.27 256.91 661.27 399.72 671.27 792 751.27 792"/></svg>}>
    Grok models — API key
  </Card>

  <Card title="zAI" icon={<svg viewBox="0 0 30 30" xmlns="http://www.w3.org/2000/svg"><path fill="currentColor" d="M15.47,7.1l-1.3,1.85c-0.2,0.29-0.54,0.47-0.9,0.47h-7.1V7.09C6.16,7.1,15.47,7.1,15.47,7.1z"/><polygon fill="currentColor" points="24.3,7.1 13.14,22.91 5.7,22.91 16.86,7.1"/><path fill="currentColor" d="M14.53,22.91l1.31-1.86c0.2-0.29,0.54-0.47,0.9-0.47h7.09v2.33H14.53z"/></svg>}>
    zAI models — API key
  </Card>
</CardGroup>

### Third-Party

Connect via API key to any of these providers:

Azure, Cerebras, DeepSeek, Groq, Moonshot, OpenRouter, Qwen, Together AI, Vercel

## Skills

Type `/` in the chat input to bring up the skills picker. All skills work with Anthropic, OpenAI, Google, and every other supported provider.

### Conversation

| Command    | Description                                                |
| ---------- | ---------------------------------------------------------- |
| `/clear`   | Clear the current conversation and start fresh             |
| `/compact` | Summarize and compress the conversation to free up context |
| `/rename`  | Rename the current conversation                            |
| `/resume`  | Resume a previous conversation                             |
| `/rewind`  | Rewind the conversation to a previous state                |

### Agentic Modes

| Command  | Description                                                            |
| -------- | ---------------------------------------------------------------------- |
| `/agent` | Switch to agent mode — the AI takes multi-step actions autonomously    |
| `/auto`  | Let the AI decide the best approach automatically                      |
| `/plan`  | Ask the AI to plan before acting, so you can review the approach first |

### Code & Review

| Command     | Description                                            |
| ----------- | ------------------------------------------------------ |
| `/add-dir`  | Add a directory to the AI's context                    |
| `/review`   | Request a code review of the current file or selection |
| `/security` | Run a security-focused review of your code             |

### Other

| Command   | Description                                                  |
| --------- | ------------------------------------------------------------ |
| `/skills` | List all available skills                                    |
| `/todo`   | View and manage todos the AI has tracked during your session |

### Usage & Stats

| Command        | Description                               |
| -------------- | ----------------------------------------- |
| `/usage`       | View token usage for the current session  |
| `/stats`       | View detailed session statistics          |
| `/extra-usage` | View extended usage and quota information |

## Chat Interface

### @ File Mentions

Type `@` in the chat input to bring up a file selection menu. Tap any file from the list to insert it as a mention — this gives the AI direct context from that file without needing to paste its contents manually.

### Code Blocks

AI responses include syntax-highlighted code blocks. Tap to:

* **Copy** - Copy code to clipboard
* **Insert** - Insert into current file
* **Run** - Execute in terminal (if appropriate)

### Messages

* **You** - Your messages appear on the right
* **AI** - Responses appear on the left with syntax highlighting

### Conversation History

Previous conversations are saved per Session. Access them by:

1. Tap the history icon in chat
2. Select a previous conversation
3. Continue where you left off

## Keyboard Shortcuts

| Shortcut      | Action                                     |
| ------------- | ------------------------------------------ |
| `Shift + Tab` | Toggle between chat input and editor focus |
| `Ctrl + S`    | Stash the current prompt to continue later |
| `Alt + V`     | Attach an image (Desktop)                  |

## GitHub Actions

Kisuke's AI chat integrates with GitHub Actions — trigger or monitor workflows directly from the chat interface without leaving your session.

## Features

### Code Context

When you're in a Session, the AI has access to:

* Your project files
* Recent terminal output
* Previous conversation history

This helps the AI give relevant, contextual answers specific to your codebase.

### Code Generation

Ask the AI to write code:

```
"Write a Python function to parse CSV files"
"Create a React component for a login form"
"Generate SQL to find duplicate records"
```

### Debugging Help

Share errors and get solutions:

```
"Why am I getting this error: [paste error]"
"My API call returns 403, what could be wrong?"
"This function returns undefined, help me debug"
```

### Code Explanation

Understand unfamiliar code:

```
"Explain what this regex does: ^[a-zA-Z0-9+_.-]+@[a-zA-Z0-9.-]+$"
"Walk me through this algorithm"
"What does this SQL query do?"
```

### Documentation

Generate docs for your code:

```
"Add JSDoc comments to this function"
"Write a README for this project"
"Document this API endpoint"
```

## Tips

### Be Specific

More detail = better answers:

```
❌ "Fix my code"
✅ "My React useEffect runs infinitely. Here's my component: [code]. How do I fix the dependency array?"
```

### Share Context

Include relevant files or errors:

```
"Looking at src/utils/parser.js, can you optimize the parse function?"
```

### Follow Up

Continue the conversation to refine answers:

```
"That works, but can you make it handle null values?"
```

## Privacy

* Conversations are sent to your chosen AI provider
* Kisuke doesn't store your chat content on our servers
* Your API credentials stay on your device


# Editor
Source: https://docs.kisuke.dev/features/editor

Edit code files on any device

## Overview

Kisuke includes a code editor with syntax highlighting, file management, and integration with AI chat — available on any device.

## Features

### Syntax Highlighting

Support for 100+ languages including:

* JavaScript / TypeScript
* Python
* Rust
* Go
* Java / Kotlin
* Swift
* C / C++
* HTML / CSS
* SQL
* And many more...

### File Browser

Navigate your project structure:

* **Tree view** - Expandable folder hierarchy
* **Quick open** - Search for files by name
* **Recent files** - Access recently edited files

### Editing

* **Auto-indent** - Smart indentation
* **Bracket matching** - Highlight matching brackets
* **Line numbers** - Easy navigation
* **Find & replace** - Search within files

## Mobile Optimizations

### Touch-Friendly

* Large tap targets
* Drag to select text
* Pinch to zoom

### Keyboard

Kisuke's keyboard includes:

* **Tab key** - For indentation
* **Symbol row** - Quick access to brackets, quotes, etc.
* **Arrow keys** - Precise cursor movement

### Quick Actions

Swipe on the editor toolbar for:

* Undo / Redo
* Comment toggle
* Format code
* AI assist

## Working with Files

### Opening Files

1. Tap **Editor**
2. Browse the file tree or use search
3. Tap a file to open

### Creating Files

1. Long-press a folder
2. Tap **New File** or **New Folder**
3. Enter the name

### Saving

Files auto-save as you type. Manual save:

* Tap the save icon, or
* Use Cmd/Ctrl+S on external keyboard

## AI Integration

### Inline Suggestions

Select code and tap **AI** to:

* Get explanations
* Request improvements
* Generate tests
* Fix errors

### Chat Context

When you open chat from the editor:

* Current file is shared as context
* Selection is included if present
* AI can see your project structure

## Media Files

Kisuke's editor can preview media files directly — no external app needed. Open any supported file from the file browser and it renders inline.

### Images

| Format | Extension       |
| ------ | --------------- |
| PNG    | `.png`          |
| JPEG   | `.jpg`, `.jpeg` |
| GIF    | `.gif`          |
| WebP   | `.webp`         |
| SVG    | `.svg`          |
| ICO    | `.ico`          |

### Video

| Format | Extension |
| ------ | --------- |
| MP4    | `.mp4`    |
| WebM   | `.webm`   |

### Audio

| Format | Extension |
| ------ | --------- |
| MP3    | `.mp3`    |
| WAV    | `.wav`    |

### Documents

| Format | Extension |
| ------ | --------- |
| PDF    | `.pdf`    |

## Editing Remote Files

When connected to a computer via Kisuke Connect:

1. Open a connected Session
2. Browse files on your remote machine
3. Edit directly — changes save to the remote file

<Note>
  Remote editing requires an active connection to the target device.
</Note>

## Tips

### External Keyboard

Connect a Bluetooth keyboard for full desktop-style editing:

* Standard shortcuts work (Cmd+S, Cmd+Z, etc.)
* Full key access
* Faster typing


# Sessions
Source: https://docs.kisuke.dev/features/sessions

Persistent project sessions across all your devices

## Overview

Sessions are how you work on projects in Kisuke. Each session is tied to a project — when you open a project (and any of its subfolders), that project gets its own session. Sessions preserve your chat history, terminal tabs, and browsing tabs across all your devices.

## Opening a Session

Sessions are created automatically when you open a project:

1. Open Kisuke
2. Tap / click **Open Project**
3. Choose a project name and location

Kisuke creates a session for that project automatically. The next time you open the same project, your session — including chat history, terminal tabs, and browser tabs — is right where you left it.

## Switching Sessions

### Mobile

Go to **Settings** to view and switch between your sessions.

### Desktop

Click **Switch / Add Session** to move between projects or open a new one.

## Session Contents

Each session contains:

* **Chat** - Your full AI conversation history, preserved across devices
* **Terminal** - Shell tabs that persist and sync between devices
* **Browser** - Browsing tabs remembered across all your devices
* **Files** - Project files and folders

## Project Detection

Kisuke automatically detects project types:

* Node.js (package.json)
* Python (requirements.txt, pyproject.toml)
* Rust (Cargo.toml)
* Go (go.mod)
* And more...

## AI Context

When you chat with AI in a session, it has context about:

* Your project structure
* Recent file changes
* Terminal history
* Previous conversations

This helps the AI give more relevant, project-specific suggestions.

## Syncing

Sessions sync automatically across all your devices:

* Chat history is preserved everywhere
* Terminal tabs persist across devices
* Browsing tabs are remembered
* File changes appear immediately


# Terminal & Shell
Source: https://docs.kisuke.dev/features/terminal

Full-featured terminal emulator on any device

## Overview

Kisuke provides a full-featured terminal emulator. Execute commands, manage processes, and navigate file systems from any device — phone, desktop, or browser.

## Features

### Full Terminal Emulation

* Complete xterm-256color emulation
* Color and Unicode support
* Session persistence across app restarts
* Multiple concurrent terminal sessions

### Customizable Themes

Choose from built-in themes or create your own:

* Dark mode optimized
* Light mode available
* Custom color schemes
* Adjustable font size

## Remote Terminal

When connected to a computer or server via Kisuke Connect:

1. Open Kisuke
2. Tap **Terminal**
3. Select your connected device
4. Full shell access is ready

### Supported Shells

* **bash**
* **zsh**
* **fish**
* **PowerShell** (Windows)
* **cmd** (Windows)

The terminal uses your default shell configuration from the remote machine.

## Keyboard

Kisuke provides a mobile-optimized keyboard with:

* **Quick keys** - Tab, Ctrl, Esc, arrows
* **Swipe gestures** - Swipe for common shortcuts
* **Full keyboard** - Access all keys when needed
* **External keyboard support** - Connect Bluetooth keyboards

### Keyboard Shortcuts

<table>
  <thead>
    <tr>
      <th>Shortcut</th>
      <th>Action</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td><code>Ctrl+C</code></td>
      <td>Interrupt</td>
    </tr>

    <tr>
      <td><code>Ctrl+D</code></td>
      <td>EOF / Logout</td>
    </tr>

    <tr>
      <td><code>Ctrl+Z</code></td>
      <td>Suspend</td>
    </tr>

    <tr>
      <td><code>Ctrl+L</code></td>
      <td>Clear screen</td>
    </tr>

    <tr>
      <td><code>Tab</code></td>
      <td>Auto-complete</td>
    </tr>
  </tbody>
</table>

## Common Use Cases

### Running Commands

```bash theme={null}
# Build your project
npm run build

# Run tests
pytest tests/

# Deploy
./deploy.sh production
```

### Server Management

```bash theme={null}
# Check logs
tail -f /var/log/app.log

# System status
htop

# Service management
systemctl status nginx
```

### Git Operations

```bash theme={null}
# Check status
git status

# Commit changes
git add . && git commit -m "Fix bug"

# Push
git push origin main
```

## Tips

### Session Persistence

Terminal sessions persist in the background. Switch between apps and come back—your session is still there.

### Quick Actions

Long-press the terminal for quick actions:

* New terminal
* Close session
* Switch sessions
* Settings


# Android
Source: https://docs.kisuke.dev/installation/android

Install Kisuke on Android

The current version of Kisuke requires Android 8.0 (Oreo) or later.

1. Download Kisuke from [Google Play](https://play.google.com/store/apps/details?id=app.kisuke).
2. Open the app and sign in with your account.
3. Grant permissions when prompted.

<Warning>
  Looking to connect your Android phone to Kisuke remotely? You'll also need [Kisuke Connect](/installation/kisuke-connect).
</Warning>


# Linux
Source: https://docs.kisuke.dev/installation/app-linux

Install Kisuke on Linux

[Download Kisuke](https://beta.kisuke.dev/downloads/) for Linux and install using the package format for your distribution.

## Supported formats

| Format   | Architecture | Best for                                                                   |
| -------- | ------------ | -------------------------------------------------------------------------- |
| AppImage | x64          | Most distributions — no install needed, just download and run              |
| `.deb`   | x64          | Ubuntu, Debian, Linux Mint, Pop!\_OS, and other Debian-based distributions |
| `.rpm`   | x64          | Fedora, RHEL, CentOS, openSUSE, and other RPM-based distributions          |

Open Kisuke and sign in with your account.

<Warning>
  Looking to connect your Linux machine to Kisuke remotely? You'll also need [Kisuke Connect](/installation/kisuke-connect).
</Warning>


# macOS
Source: https://docs.kisuke.dev/installation/app-macos

Install Kisuke on macOS

The current version of Kisuke requires macOS 12 (Monterey) or later.

1. [Download Kisuke](https://beta.kisuke.dev/downloads/) for macOS.
2. Open the `.dmg` and drag **Kisuke** into your Applications folder.
3. Open Kisuke from Applications and sign in with your account.

<Warning>
  Looking to connect your Mac to Kisuke remotely? You'll also need [Kisuke Connect](/installation/kisuke-connect).
</Warning>


# Windows
Source: https://docs.kisuke.dev/installation/app-windows

Install Kisuke on Windows

The current version of Kisuke requires Windows 10 (1903) or later.

1. [Download Kisuke](https://beta.kisuke.dev/downloads/) for Windows.
2. Run the installer.
3. Open Kisuke and sign in with your account.

<Warning>
  Looking to connect your PC to Kisuke remotely? You'll also need [Kisuke Connect](/installation/kisuke-connect).
</Warning>


# CLI
Source: https://docs.kisuke.dev/installation/cli

Install Kisuke Connect via CLI for servers and headless environments

The CLI is the headless version of Kisuke Connect — the same daemon, without the desktop GUI. Use it for servers and automated environments.

## Install

```bash theme={null}
npm install -g @kisuke/cli@dev
```

On macOS, you can also install via Homebrew:

```bash theme={null}
brew install kisukeapp/tap/kisuke-cli-dev
```

## Run

Once installed, run `kisuke connect` in your terminal:

```bash theme={null}
kisuke connect
```

To see all available commands, run `kisuke` by itself:

```bash theme={null}
kisuke
```

On first run, the CLI will walk you through setup. It starts by checking your system and asking you to agree to the terms:

```
┌  Kisuke Connect v1.1.84
│
◇  Daemon is not running
│
◇  Preflight checks passed
│
●  Before installing, please review our terms and privacy policy:
│
│    Terms:   https://beta.kisuke.dev/terms
│    Privacy: https://beta.kisuke.dev/privacy
│
◇  Do you agree to the Terms of Service and Privacy Policy?
│  Yes
```

Once you agree, the daemon is installed and started:

```
◇  Daemon installed
│
◇  Daemon started
```

A browser window opens for you to sign in with Google or GitHub:

```
◇  Opening browser for authentication...
│
◇  Authentication successful
│
◆  Logged in as you@example.com
│
◆  Daemon running (PID 63348)
│
└  Done
```

<Warning>
  Having trouble authenticating on a VPS or headless server? See [CLI Troubleshooting](/troubleshooting/cli).
</Warning>


# iOS
Source: https://docs.kisuke.dev/installation/ios

Install Kisuke on iOS

The current version of Kisuke requires iOS 15.0 or later.

1. Download Kisuke from the [App Store](https://apps.apple.com/app/kisuke).
2. Open the app and sign in with your account.
3. Grant permissions when prompted.

<Warning>
  Looking to connect your iPhone to Kisuke remotely? You'll also need [Kisuke Connect](/installation/kisuke-connect).
</Warning>


# Install Kisuke
Source: https://docs.kisuke.dev/installation/kisuke



New users can follow the [Quickstart](/quickstart) guide to set up Kisuke and Kisuke Connect in minutes.

## Install instructions

The following topics provide platform-specific installation instructions for the Kisuke app.

* [Install on iOS](/installation/ios)
* [Install on Android](/installation/android)
* [Install on macOS](/installation/app-macos)
* [Install on Windows](/installation/app-windows)
* [Install on Linux](/installation/app-linux)
* [Use the Web App](https://web.kisuke.app) — no install needed, open Kisuke directly in your browser

## Next steps

Once you've installed Kisuke, install [Kisuke Connect](/installation/kisuke-connect) on the computer you want to access remotely.


# Install Kisuke Connect
Source: https://docs.kisuke.dev/installation/kisuke-connect



New users can follow the [Quickstart](/quickstart) guide to set up Kisuke and Kisuke Connect in minutes.

## Install instructions

The following topics provide platform-specific installation instructions for Kisuke Connect.

### Desktop

* [Install on macOS](/installation/mac)
* [Install on Windows](/installation/windows)
* [Install on Linux](/installation/linux)

### CLI

* [Install CLI](/installation/cli) — for servers, containers, and headless environments

## Update

### Desktop

To update Kisuke Connect, download the latest version from the [Kisuke downloads page](https://beta.kisuke.dev/downloads/) and run the installer again.

### CLI

```bash theme={null}
kisuke update
```

## Uninstall

To uninstall Kisuke Connect, remove it using the same method you used to install it (e.g., drag to Trash on macOS, uninstall from Settings on Windows, or `apt remove kisuke-connect` on Linux).


# Linux
Source: https://docs.kisuke.dev/installation/linux

Install Kisuke Connect on Linux

The current version of Kisuke Connect requires Linux kernel 4.19 or later.

[Download Kisuke Connect](https://beta.kisuke.dev/downloads/) for Linux and install using the package format for your distribution.

## Supported formats

| Format   | Architecture | Best for                                                                   |
| -------- | ------------ | -------------------------------------------------------------------------- |
| AppImage | x64          | Most distributions — no install needed, just download and run              |
| `.deb`   | x64          | Ubuntu, Debian, Linux Mint, Pop!\_OS, and other Debian-based distributions |
| `.rpm`   | x64          | Fedora, RHEL, CentOS, openSUSE, and other RPM-based distributions          |

Open Kisuke Connect — a sign-in window will appear. Sign in with **Google** or **GitHub** using the same account you use in Kisuke.

After signing in, Kisuke Connect will live in your **system tray** — look for the Kisuke Connect icon in your panel's notification area.

<Info>
  Prefer the command line? You can also install Kisuke Connect via [CLI](/installation/cli).
</Info>

## Troubleshooting

If the system tray icon does not appear, make sure your desktop environment supports system tray icons (e.g., install `gnome-shell-extension-appindicator` on GNOME).


# macOS
Source: https://docs.kisuke.dev/installation/mac

Install Kisuke Connect on macOS

The current version of Kisuke Connect requires macOS 12 (Monterey) or later.

1. [Download Kisuke Connect](https://beta.kisuke.dev/downloads/) from the Kisuke website.
2. Run the installer. If you have a previous version installed, you may be prompted to uninstall it first.
3. Choose an install location and complete the installation.
4. Open Kisuke Connect — a sign-in window will appear. Sign in with **Google** or **GitHub** using the same account you use in Kisuke.
5. After signing in, Kisuke Connect will live in your **menu bar** — look for the Kisuke Connect icon in the top-right corner of your screen.

<Info>
  Prefer the command line? You can also install Kisuke Connect via [CLI](/installation/cli).
</Info>

## Troubleshooting

If Kisuke Connect does not appear in the menu bar, check that it is running by searching for "Kisuke Connect" in Spotlight.


# Windows
Source: https://docs.kisuke.dev/installation/windows

Install Kisuke Connect on Windows

The current version of Kisuke Connect requires Windows 10 (1903) or later.

1. [Download Kisuke Connect](https://beta.kisuke.dev/downloads/) from the Kisuke website.
2. Run the installer. If you have a previous version installed, you may be prompted to uninstall it first.
3. Choose an install location and complete the installation.
4. Open Kisuke Connect — a sign-in window will appear. Sign in with **Google** or **GitHub** using the same account you use in Kisuke.
5. After signing in, Kisuke Connect will live in your **system tray** — click the **^** arrow in the bottom-right corner of your taskbar to find the Kisuke Connect icon.

<Info>
  Prefer the command line? You can also install Kisuke Connect via [CLI](/installation/cli).
</Info>

## Firewall (optional)

Kisuke Connect may prompt you to allow network access. Click **Allow** when the Windows Firewall dialog appears.

If you need to configure the firewall manually:

1. Open **Windows Defender Firewall**
2. Click **Allow an app through firewall**
3. Find **Kisuke Connect** and enable both Private and Public networks

## Troubleshooting

If Kisuke Connect does not appear in the system tray, check the overflow area by clicking the **^** arrow in the taskbar.


# Quickstart
Source: https://docs.kisuke.dev/quickstart

Get Kisuke running in minutes

## 1. Install Kisuke

Download Kisuke on your phone or desktop:

<CardGroup>
  <Card icon="apple" href="https://beta.kisuke.dev/downloads/" title="iOS">
    Download for iPhone / iPad
  </Card>

  <Card icon="google-play" href="https://beta.kisuke.dev/downloads/" title="Android">
    Download for Android
  </Card>

  <Card icon="desktop" href="https://beta.kisuke.dev/downloads/" title="Desktop">
    Download for macOS, Windows, or Linux
  </Card>

  <Card icon="globe" href="https://web.kisuke.app" title="Web">
    Open in your browser — no install needed
  </Card>
</CardGroup>

## 2. Sign in

Open Kisuke and sign in with **Google** or **GitHub**. This creates your account and links your device.

## 3. Install Kisuke Connect

Kisuke Connect runs on the computer you want to access remotely. It bridges your terminal, files, and editor to Kisuke over an encrypted connection.

<CardGroup>
  <Card icon="display" href="https://beta.kisuke.dev/downloads/#connect" title="Desktop App">
    macOS, Windows, or Linux
  </Card>

  <Card icon="terminal" href="/installation/cli" title="CLI">
    For servers and headless environments
  </Card>
</CardGroup>

## 4. Sign in to Kisuke Connect

Sign in with the **same account** you used in step 2. Once both devices are signed in, they automatically connect.

## 5. You're connected

Open Kisuke on your phone or browser and start using:

* [Chat](/features/coding-with-ai) — code with AI assistance
* [Terminal](/features/terminal) — full shell access from anywhere
* [Code Editor](/features/editor) — edit files with syntax highlighting
* [Browser](/features/browser) — browse the web on your remote machine

No port forwarding. No firewall rules. No VPN. Just sign in and go.


# What is Kisuke?
Source: https://docs.kisuke.dev/what-is-kisuke

Kisuke is your favourite pocket engineer.

Your best ideas don't wait — so Kisuke brings a full development environment to wherever you are, whether that's your phone, your laptop, or your desktop. Write code, run commands, and chat with AI assistants on iOS, Android, macOS, Windows, Linux, and the web.

## Kisuke vs Kisuke Connect

Kisuke has two parts that work together:

|                  | Kisuke                                                                                                        | Kisuke Connect                                  |
| ---------------- | ------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
| **What it is**   | The app you use                                                                                               | Desktop / server daemon                         |
| **Runs on**      | iOS, Android, macOS, Windows, Linux, Web                                                                      | macOS, Windows, Linux, servers                  |
| **Role**         | The client you use                                                                                            | The server you connect to                       |
| **Install from** | TestFlight (iOS), Google Play, [downloads](https://beta.kisuke.dev/downloads/), [web](https://web.kisuke.app) | [downloads](https://beta.kisuke.dev/downloads/) |

**Kisuke** is the app you use on any device — phone, tablet, desktop, or browser. **Kisuke Connect** is a lightweight background daemon that runs on your desktop or server and exposes your terminal, files, and editor to the app — over an end-to-end encrypted connection across 14+ global regions.

You sign in to both with the same account and they find each other automatically.

## Use Cases

* **Mobile development** - Code while commuting or traveling
* **Desktop development** - Full IDE-like experience on macOS, Windows, or Linux
* **Server management** - Connect to servers from any device via Kisuke Connect
* **Quick fixes** - Make hotfixes from your phone, tablet, desktop or browser
* **Learning** - Practice coding with AI assistance anywhere