Editor

When a project is open, the main workspace includes the file tree, code editor, terminal, dependency panel, and AI panel. How these are arranged depends on the active view mode.

View modes

Ssscript has two primary view modes, plus a compact dock window:

Mode	Shortcut	Description
Agent (simplified)	⌘1 / Ctrl+1	Full-screen AI panel with a conversation-first workflow. The file tree and editor are hidden; you interact through prompts.
Code	⌘2 / Ctrl+2	Split layout with the file tree, code editor, and AI panel side by side. All panels are resizable and collapsible.
Mini dock	⌘3 / Ctrl+3	A compact floating window showing connectivity status, dev-server state, and a minimal AI interface. Useful for keeping Ssscript accessible while working in another app.

Your last-used view mode is remembered across sessions. The mini dock window runs alongside the main window — toggling it does not close your main workspace.

File tree

• Browse and open files in the project. Only editable paths (e.g. under src/, certain config files) can be opened for editing; others are read-only or excluded.
• Click a file to open it in the code editor. The editor shows one file at a time.
• Right-click (or long-press) a file or folder to open the context menu:
  • New File — create a file inside the selected folder (or the project root).
  • New Folder — create a subfolder.
  • Delete — remove a file or folder.
• Toggle the file tree with ⌘B / Ctrl+B (Code view only).

Quick Open

Press ⌘P / Ctrl+P to open Quick Open — a fuzzy file finder that lets you jump to any project file by typing part of its name. Press Enter to open the selected file, or Escape to dismiss.

Command palette

Press ⌘⇧P / Ctrl+Shift+P to open the Command palette. It provides a searchable list of actions — for example, creating a new file with a multi-step flow (choose parent directory, then enter a name).

Code editor

• CodeMirror with TypeScript support (syntax, basic intelligence). Theme and keybindings follow the app defaults.
• Search — Find in file; history and undo/redo are available.
• Edits are saved to disk. The app manages which paths are writable to keep the project structure intact.

Terminal

• Install — Run bun install in the project (e.g. after adding or removing dependencies).
• Run — Start the dev server (e.g. bun run dev). Logs stream in the terminal; you can stop the process from the app.
• Build — Run the project build (e.g. bun run build) to produce bundles for deployment.

Install runs automatically when you open a project if dependencies aren’t installed yet.

Toggle the terminal with ⌘J / Ctrl+J or Ctrl+`.

Dependencies

• Add — Search the npm registry and add packages to dependencies (or optionally devDependencies). Uses Bun to modify package.json and run install.
• Remove — Remove non-core dependencies. Core dependencies (defined by the starter template) are kept.

Dependency changes are reflected in the terminal output and in the file tree once package.json is updated.

Layout

• All panels (AI, files, terminal) are resizable by dragging their borders and collapsible.
• Panel sizes and collapsed states are persisted across sessions.
• Text scale — Increase (⌘+), decrease (⌘-), or reset (⌘0) the global UI text size.
• Publish and Embed actions are available from the terminal area when you’re signed in and the project is publishable.