LLM interaction

Sessions and colors

npx inbase run opens 11 empty chat slots on the map. Each slot has a color.

LLM session colors

ColorCommandAlias
Blue/blue/sky
Coral/coral/red
Amber/amber/yellow
Lime/lime/green
Orange/orange
Violet/violet/purple
Teal/teal
Crimson/crimson
Forest/forest/darkgreen
Grey/grey/gray
White/white

/connect attaches to the first enabled blueprint (by color order). A color command still picks that slot directly.

Connect a chat by starting with /inbase (next empty slot), /connect (first enabled blueprint), a color command, and your request:

Color command with request

That attaches the chat to that color’s empty slot — Coral in the example above.

A regular chat without /inbase, /connect, or a color command does not attach. Keep using those commands when you want the map session.

When a chat is attached, the map opens that color’s LLM session window. Look for ATTACHED / LLM CONNECTED and the current status (for example “LLM is planning steps”):

LLM session window attached

Blue is the first color. It works like the others: pick it, draw on it, and connect with /blue.

Drawing a blueprint

You draw a blueprint on top of the map — the spatial plan the LLM follows as closely as possible. It may add files the drawing does not cover when they are needed. Place it before a chat connects, or keep adding after the chat has attached.

Pick a session color in the row above the session window to draw on that color’s blueprint. Hide, Clear, and Cleanup apply to the active color.

Add folders

Right-click a folder on the map and choose Add folder. For example, plan a components folder under src:

  1. Open the context menu and choose Add folder:

Add folder from the map context menu

  1. Enter the name and choose which blueprint color it belongs to:

Name the folder and pick a session color

  1. The planned folder appears on the map in that color:

Planned components folder on the map

Add files

Right-click a folder and choose Add file. For example, RandomColorGenerator.tsx inside components:

  1. Open the context menu and choose Add file:

Add file from the folder context menu

  1. Enter the file name (it is created in that folder on the active blueprint):

Name the planned file

  1. The file block appears on the map. Click it to open the info panel:

Planned file on the map with info panel

Add classes, functions, and vars

In the info panel, add the classes, functions, and vars the file should contain. The LLM treats those symbols as part of the blueprint.

On a file with no classes, type a function or variable name and click Add:

Add functions and vars in the info panel

On a class file, type a name in Class name and click Add. Under that class, add func and add var open a name field for a method or field. Those members stay indented under the class.

You can also add imports, or a note on a symbol for extra instructions or pseudo code.

File notes

Use a file note for free-form instructions the LLM should follow for that file. In the info panel, click Add file note:

Add file note button

Write what the file should do, then close the note:

File note editor

Session specific blueprint

Each color is its own blueprint. Only the chat attached to that color receives that layer. Blue is first and works the same way.

When you add a folder or file, pick a session color at the bottom of the dialog:

Choose a session color

Planned items take that color on the map. Here components is on Blue and session-specific belongs to Coral (red):

Session-colored folders on the map

Multiple session blueprints

Left to right: the first folder is local to /coral, the second is local to /amber, and the blue folder belongs to /blue.