Creytix
Sign in
Creytix IDEPreview

Workspace layout

File tree, editor, and the tabbed Browser, Terminal, and Git surfaces that make up the IDE.

AI

Preview — early access.

Overview

Every part of the IDE is scoped to one workspace root at a time — the file tree, the editor, the terminal, and the git panel all read and write against whichever workspace you have open, shown as a 📁 chip in the header.

How it works

The file tree on the left lists the workspace root; expand a folder to load its children, and hover a file or folder for inline Rename/Delete (folders also get + File / + Folder). The editor in the center is Monaco — full syntax highlighting by file extension, Cmd/Ctrl+S to save, and a dirty-dot on any unsaved tab. Across the top of the editor pane sit your open file tabs plus six persistent surfaces:

  • Browser — an embedded page preview with its own console feed and an element picker that can hand a clicked element straight to the AI agent as an instruction.
  • Terminal — runs each command through zsh -lc in the selected workspace and streams the output back.
  • Git — status, diff, stage, and commit/push against the selected workspace's repo.
  • Routines, Secrets, Models, Chats — each covered on its own page (linked below).

Steps

  1. •

    Confirm your workspace

    Check the 📁 chip in the header; click it to switch workspaces (unsaved changes prompt for confirmation first).

  2. •

    Open a file

    Click a file in the tree, or use the search box to jump to it by name.

  3. •

    Switch surfaces

    Click Browser, Terminal, Git, Routines, Secrets, Models, or Chats in the tab strip — they sit alongside your open file tabs.

  4. •

    Save your work

    Cmd/Ctrl+S saves the active file; the dirty dot clears once it lands.

  5. •

    Check in with git

    Open the Git tab to see status and diffs, then stage and commit from there.

Capabilities

  • Inline file management — create, rename, and delete files and folders without leaving the tree.
  • Real-time collaboration — a "Collab" toggle on the open file shares live edits with named peers when the collab server is reachable.
  • Element-to-agent picking — pick an element in the Browser tab and send it straight into an agent instruction.
  • Git without a terminal — status, diff, stage, commit, and push from the Git tab; noisy fleet-automation paths (staging queues, heartbeat files) are hidden by default.

Limits & honest scope

These are working panes, not full IDE parity with a desktop editor.

  • The terminal is a command-runner, not a PTY — interactive, full-screen terminal programs (vim, htop, less) aren't supported yet.
  • The Browser tab previews through a proxy; some sites or paths may not render correctly inside it.
  • The Git tab operates on one workspace repo at a time, not a multi-repo view.
  • Real-time collaboration falls back to solo mode if the local collab server isn't running — it won't block you from editing.

Related