Setup and Requirements

Requirements

• The RPC server is part of the Cubit graphical application. An RPC session therefore requires the GUI and a display. It cannot be run headless, and -rpc has no effect when combined with -nogui.
• Only one RPC-enabled Cubit session can run on a machine at a time. See One session, one driver below.
• The cubitc client is a standard-library Python 3 script. It requires a Python 3 interpreter on the host, but no Python packages and no access to Cubit's own libraries.

Starting an RPC-enabled Session

From the Cubit installation root, launch the GUI with the -rpc option:

cd /path/to/Coreform-Cubit-2026.8

./coreform_cubit -rpc

The server listens on port 50505. If the session does not behave as expected once it is running, see Troubleshooting, which covers how to confirm that the listener is up and that the session accepts commands.

Pointing an LLM Agent to the Cubit Session

Any LLM agent that can run shell commands can drive the session. Tell it where the client is and that a session is running — a prompt as short as "use <install>/bin/cubitc to drive the running Cubit session" is enough for an agent to connect and begin issuing commands.

Driving Cubit

After that initial instruction, users can issue natural-language requests and instructions via the LLM agent to drive Coreform Cubit actions and processes, retrieve model and mesh information, and create and iterate on scripted workflows.

The model itself lives in the Cubit session, not in the client or in the agent. Each cubitc invocation opens a connection, sends one request, reads the response, and closes; nothing is held between invocations. Closing a terminal or restarting the agent therefore loses no work, and the GUI shows the current state of the model at every point during a session.