Tiles
Download
Skip to Content
Manual

Manual

Reminder: this is in alpha.

Enjoy these sample commands in lieu of a formal doc.

Tiles

Commands in this section are for regular users. Most day-to-day behavior is also available as slash commands inside the chat REPL.

Commands are grouped by subcommand family: the base tiles command, identity, data layout, models, updates, then peer-to-peer linking and sync.

Main command (tiles)

Launches onboarding (first run) and the interactive REPL.

This is what the first run looks like when you type tiles in your terminal.

Tiles onboarding flow in the CLI
Click to expand

First-run onboarding flow (tiles)

tiles   # Onboarding (if needed) and REPL

Account (tiles account)

Root identity and display nickname.

tiles account create [<nickname>]  # Create root identity (nickname optional)
tiles account set-nickname         # Set nickname
tiles account                      # Show account details
tiles account create alice
tiles account set-nickname
tiles account

Data directory (tiles data)

Where Tiles stores local data.

tiles data set-path <path>   # Set data directory
tiles data set-path ~/.tiles/data

Run models (tiles run)

Start a chat session with a model; optional Modelfile path and experimental memory flag.

tiles run [MODELFILE_PATH]   # Default model if path omitted
tiles run -m                 # Experimental memory model
tiles run
tiles run ./path/to/Modelfile
tiles run -m

App updates (tiles update)

tiles update   # Check for and install app updates

Tiles can sync chats across multiple linked devices peer-to-peer, with or without the internet. Linking is a one-time step so both sides consent before any sync traffic is accepted; you do not need to re-link each time you sync.

tiles link enable      # Become link listener; share the ticket out of band
tiles link list-peers  # Show linked peers (DID and nickname)
tiles link disable     # Unlink a peer; ignore their future sync requests

tiles link enable: Puts this device in link listener mode. It generates a link ticket and waits for a link request from another device. Share the ticket out of band with the peer you want to link.

  • If the device is online, the ticket is a base64 string (easy to copy).
  • If offline, the ticket is an eight-character alphanumeric code you can type on another device on the same network.

When the peer runs tiles link enable and supplies your ticket, this device is notified; after you approve, the two devices are linked.

tiles link list-peers: Lists linked peers by DID (decentralized identifier) and nickname.

tiles link disable: Unlinks a peer. Future sync requests from that peer are ignored.

Peer-to-peer: chat sync (tiles sync)

After devices are linked, use tiles sync to replicate chats. Listener and initiator roles mirror linking: one side waits, the other connects using the listener’s DID.

tiles sync        # Listener: wait for incoming sync requests
tiles sync <DID>  # Initiator: sync toward the peer with this DID (the listener)

tiles sync (listener): Starts this device in sync listener mode: it waits for incoming sync requests.

On the other device, run tiles sync with the listener’s DID so the initiator targets the correct peer. If your CLI uses different syntax for the peer argument, check tiles sync --help.

When a sync run finishes, you should get a notification on the devices involved.