RailCall Chat

Connect Chat to your station

Install or update the station, then start it. Keep that terminal open while using Chat.

curl -fsSL https://railcall.ai/install.sh | bash
railcall version
railcall studio

Download Chat from Chat downloads. On a Mac, choose Apple Silicon for an M-series chip or Intel for an Intel processor. Open Chat and connect to the local station. Use the station URL printed by the terminal if you need to open Studio.

Start with Auto, the recommended routing option. It chooses from the model routes available to your station under its policy. You still need a local model, an authorized collaborator, or a supported cloud key. See Models & Auto before enabling remote reasoning.

Start with an answer, then generate a PDF

First ask a short question to confirm that your chosen model responds. Then try a task with an explicit output and a clear boundary:

Using only the notes below, compare three rollout options for a
small support team. Explain assumptions, risks, and a recommendation.
Generate a PDF with a comparison table and a two-week rollout checklist.
Save it locally. Do not email or post it.

Notes:
- Four support agents handle 300 tickets each week.
- Start with drafting replies; every outbound reply needs approval.
- Pilot with one agent for one week before expanding.
- Track time saved, corrections, and failed runs. Do not invent results.

The model prepares the content; a PDF export action creates the file. Depending on installed capabilities, export can use the native action or a document-generation module. A written plan or a file name in a reply is not proof of export: open the actual artifact and check the text, tables, and assumptions.

For research tasks, explicitly request source links and inspect them. Web search and fetching pages are network operations. A generated PDF does not establish that its claims or calculations are correct.

Review actions before execution

For an integration request, inspect the editable action card: destination, content, required fields, and preview result. Missing credentials or inputs must be resolved before approval. An unconfigured preview is not a successful send. External sends require your approval; inspect the resulting status and receipt.

Save & run a workflow

In Studio Builder, compose a workflow and inspect each step. In the documented release, Save & run supports linear workflows whose steps are bound to commands. Missing bindings, required inputs, blocked previews, and unsupported conditional paths stop the runner. Complete setup and review before running again.

This is a manual run. It does not activate a recurring schedule or make a chat keyword into a persistent trigger. Use the station's workflow and scheduling controls where supported, and verify a real run before relying on unattended execution.

Optional hosted RailCall Assistant

RailCall Assistant is a separate, hosted preview option. It uses RailHub and a host station, such as Patrik's computer, with local models and potentially service-funded external reasoning. It is not the same as ordinary Auto on your own station.

Sign in with railcall market login, then reopen the model list. Availability depends on the service, worker health, queue, and usage limits; a visible entry does not guarantee a ready worker. Shared hardware has limited capacity, so requests may wait or be refused.

The preview admission window ends at 00:00 UTC on 15 September 2026 (free through 14 September). It does not automatically convert to a paid subscription. Check the disclosure shown before submitting; read data boundaries and retention.

If setup, a model, or an export fails, use Troubleshooting. General crash recovery and arbitrary workflow resume are not promised by this release.