Skip to main content
Use Settings to choose how you want to work in Kisuke. Start with General for the Zen launch default and composer behavior, or Appearance for theme, typography, editor, and terminal controls. The main instructions below cover desktop and web. Mobile settings use a different arrangement.

​
Open and search Settings

Open Settings from the workspace, or press Ctrl+Shift+J. This shortcut uses Control on macOS too. Type in Search settings to narrow the sections in the sidebar. For example: Select a matching section to open it. Clear the search to show all sections again. When finished, choose Back to app to return to your workspace.
Settings search matches section names and a set of keywords. It does not search every word in every panel. Searching for Zen currently returns no matches; open General directly to find the launch default.

​
Make Zen your launch layout

1

Open General

In Settings, select General and find Default workspace mode.
2

Choose Zen

Select Zen to use the conversation-centered layout when Kisuke opens. Select Classic if you prefer the traditional editor and terminal layout.
3

Return to the workspace

Choose Back to app. The launch preference does not switch the layout you are currently using.To enter Zen now, choose Switch layout → Zen in the workspace’s top bar. Press Escape if the menu stays open.
A temporary switch between Zen and Classic leaves the saved launch preference unchanged. Use Zen mode to learn the sidebar, right panel, and environment controls. For a keyboard route, open the command palette with Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows and Linux, search for Toggle Zen Mode, and press Enter. This toggles the current layout: if you are already in Zen, it takes you to Classic.

​
Keep Worktree style separate

General → Work mode offers Classic and Worktree style. This is a separate preference from Default workspace mode. Choosing Classic in the Work mode group turns off Worktree style. It does not select Classic as the launch layout. Read the group title to distinguish the two Classic cards. Worktree style gives worktree conversations more room by hiding the sidebar and right panel when enabled inside a worktree. You can reopen the panels you need. It does not create a worktree; follow Work in a separate checkout when you want another working folder and branch.

​
Adjust the composer

In General, start with these controls:
  • Send messages with: choose Enter or Cmd/Ctrl+Enter. With Enter selected, Shift+Enter inserts a newline. With Cmd/Ctrl+Enter selected, Enter also inserts a newline.
  • Follow-up behavior: choose Queue for another instruction after the current turn, or Steer to request a change of direction while the agent works. Delivery depends on the harness and the conversation’s state.
  • Composer → Auto-convert long paste threshold: set the character count at which a paste becomes a text attachment. A value of 0 disables automatic conversion.
Read Queue and steer follow-ups for the alternate send shortcut and delivery limits. See Attach files and paste long text for reviewing attachments before sending. General also contains completion sounds, Always show context usage, and Show MCP status in chat. Enable Always show context usage to keep the desktop/web composer indicator visible below its usual 70% threshold; see context usage and its estimates. The separate task prompt template applies when starting task work. These layout and composer choices have no page-wide Save button. Controls that edit a larger configuration, such as a task template or hidden-file patterns, have their own save or apply action.

​
Notifications and sounds

Attention notifications tell you that a conversation needs a decision. The desktop completion sound tells you that a response stopped streaming. Keep these separate when deciding whether to return to a chat: neither verifies the agent’s work or replaces reading its result.

​
Enable desktop attention notifications

  1. Open Settings → Notifications.
  2. Turn on Enable desktop notifications.
  3. Allow Kisuke notifications in your operating system if prompted. Also check the operating system’s notification settings if the switch is on but banners do not appear.
  4. Return to the workspace. These alerts are intended for when the Kisuke window is not focused; while you are using it, read the request in the conversation.
Notifications can identify a permission request, a structured question, or a plan awaiting review. An ordinary question written in the agent’s response does not create a structured question alert. Click an alert to return to its conversation, then inspect the full request before responding. A banner can contain a filename, part of a command, or question text; use your operating system’s notification-preview controls if you do not want that information visible on screen. The desktop switch and the operating system’s permission are separate. The switch can remain on even when the operating system blocks delivery. The current browser client’s Settings sidebar does not expose the same Notifications entry, so the steps above apply to the desktop app.

​
Enable phone notifications

On iOS or Android, sign in and open Settings → Notifications → Enable Notifications. Allow notifications in the system prompt. If a previous denial sends you to system settings instead, enable Kisuke notifications there, return to the app, and check the switch again. If it remains off, turn it on after granting system permission. The phone can notify you about permission requests, questions, and plan reviews. On Android, an alert can also appear while you are looking at a different conversation; the app suppresses the local alert for the selected conversation. On iOS, do not rely on a system banner while Kisuke is in the foreground: open the conversation and check its pending request. Tap the notification body to open the conversation. Buttons such as Allow or Approve are decisions, not just navigation. Open the conversation first when you need to inspect the full request. If its computer is offline, restore the device connection and check the current request before responding. An enabled switch does not verify remote push delivery. The phone also needs system permission and a working signed-in connection to register for pushes. To mute alerts at the phone level, turn off Kisuke notifications in the phone’s system settings.

​
Choose a desktop completion sound

  1. Open Settings → General → Sound & power.
  2. Enable Sound effects. This reveals Completion sound.
  3. Choose Test to hear the selected sound. The initial choice is Built-in tone.
  4. To use your own clip, choose Choose file… and select a .wav, .mp3, or .mp4 file up to 2 MB. After a successful save, the control shows Custom — and the filename. Use Test to check playback.
  5. Choose Remove to return to the built-in tone, or turn off Sound effects to stop automatic completion sounds.
The custom clip is stored in the current client’s local storage. Choose it separately on another client; Device Sync is not a way to distribute this audio file. Automatic completion sounds are currently available in the desktop app. A tone can play when a chat stops streaming, including after an interruption or an error, even if you are viewing another chat. Read the response and check its actual result; a tone does not mean tests passed, changes were committed, or a goal finished. The web client’s Test control can preview a sound, but automatic playback after a response is not currently available there.

​
If an alert or sound is missing

​
Find appearance, editor, and terminal controls

On desktop and web, open Appearance. The panel includes: Choose the font-size control for the surface you want to adjust. UI, code, and terminal sizes are separate preferences. For file visibility and language support, use Files and editor. For the scope and timing of question previews, use Answer questions. Keybindings is a searchable shortcut reference. Its rows show commands, key combinations, and any focus conditions; it does not provide a shortcut-remapping editor. The keyboard reference covers common workspace and composer actions.

​
Find agent, project, and device settings

Use the section that owns the choice you want to make: Before changing project, provider, or Git configuration, check the selected project and device. A preference on your current client and configuration on the computer running the agent can have different scopes. Use the model picker for the current conversation’s model and reasoning selection. A picker choice is submitted for validation with the next prompt; it does not reconfigure a turn that is already running. A new provider connection also does not make every model available through every harness.

​
Find settings on mobile

The iOS and Android settings screen has separate Appearance, Chat, Editor, and Terminal destinations:
  • Chat includes question-preview format and Allow new worktree creation from chat.
  • Editor includes file visibility, language intelligence, word wrap, font size, and tab size.
  • Terminal includes font size, cursor blink, and the command bar.
Use the mobile destination labels instead of looking for the desktop Appearance panel’s full set of groups. The Zen/Classic launch picker described above belongs to desktop and web. In the tablet Zen workspace, tap Show chat list, then Settings beside the search field. Tablet layout selection follows the available window size automatically. To sign out on a phone or tablet, open Devices → Account options → Sign out. See Sign out of your phone or tablet for its scope and recovery.

​
If a setting is hard to find or does not stick

Clear the query and open the section directly. Try a broad term such as font or composer. In particular, use General for the Zen launch default.
Default workspace mode affects how Kisuke opens. Choose Switch layout → Zen to enter Zen now. The command palette’s Toggle Zen Mode changes the current layout in either direction, so it can take you out of Zen if you are already there.
Check whether that control has a separate Save or Apply action. Reopen the same section in the same client and confirm the selected value. For project or device settings, confirm that you are still looking at the same destination.If a local preference is lost after restarting, report the setting name, client, and whether it changed before or after restart. Avoid clearing app data as a first recovery step.
Check the corresponding setting on that device. Do not assume every workspace or display preference is copied by Device Sync; that feature has specific categories for agent configuration. Follow its guide to inspect the source computer, destination, and sync status.