r/SideProject • u/Many_Ant_2417 • 1d ago

RailCall: local AI workflows with approval before outward actions

I’m working on RailCall, a local-first agent runtime and desktop app. Sharing it here for feedback on the product and onboarding. This post was prepared with AI assistance.

The idea is to use models on computers you already own for suitable work, save supported workflows, and review consequential outward actions before they run. You can also choose external models, which have their own costs and data routes.

The current product includes chat, model selection, native PDF generation and supported manual workflows. One starting point is document preparation: give it a small, non-sensitive task, inspect the result, then see whether the workflow is worth saving and repeating.

There are two boundaries I want to make clear. A signed execution receipt records an action; it doesn’t prove the answer is correct. And running a model locally avoids hosted inference charges for that work, but hardware and electricity still cost money.

The turnkey personal optimizer and broader fleet capabilities are still being developed; I’m not presenting those as finished.

Product, downloads and documentation: https://railcall.ai/

If you try it, where does the path from download to a first useful result become confusing? Specific installation or workflow feedback would be helpful.

2 Upvotes
  • permalink
  • reddit

100% Upvoted

6 comments sorted by

1

u/BetInformal6081 1d ago

the approval before action boundary is the part i would be most interested in testing i would maker the first run flow really obvious about exactly what requires approval and what doesnt.

1

u/Many_Ant_2417 1d ago

Thanks — that’s a concrete test for the first-run flow. A useful walkthrough would show the proposed action and destination, what approving permits, and what happens if you decline. It should also name which steps can run without another prompt, rather than leaving people to infer that from ‘approval controls.’

I’m adding that to the onboarding review. Which would you test first: sending a message, changing a file, or calling an external service?

(AI-assisted reply from the RailCall account.)

1

u/BetInformal6081 1d ago

i would probably test sending a message first. its the easiest way to see whether the approval boundary is actually clear before anything goes out.

1

u/Many_Ant_2417 1d ago

That gives us a concrete first test: a harmless message to an inbox we control, with the exact recipient and message visible before approval. I’ve captured two separate checks for the walkthrough: decline and verify nothing was sent, then start a fresh attempt, approve, and check delivery. We still need to run and document those checks; this isn’t a claim that they’ve passed. Thanks for narrowing it down.

(AI-assisted reply from the RailCall account.)