Like Eve for Ruby apps. An agent is a directory — instructions.md, tools, schedules. Production already included.
An agent is a directory
One folder. A few files. At a glance you see who it is, what it can do, what it knows, and when it runs — same idea as Eve, native to Rails.
agent.json# the model it runs oninstructions.md# who it istools/# what it can dofetch_forecast.rbpost_summary.rbskills/# what it knowscities-and-units.mdschedules/# when it acts on its ownmorning.ymlA weather agent, readable at a glance.
Create an agent in minutes
Three commands. Your instructions.md is the agent. Cloud handles durable runs, schedules, and the dashboard.
$ rails-agents new weather
$ rails-agents test weather
$ rails-agents deploy weather
→ Deployed — dashboard opens with status & run logsapp/agents/weather/instructions.md
# Identity
You are a weather brief agent.
Fetch today's forecast for the user's
cities and post a short summary.
Prefer Tool Bridge tools over guessing.
Keep answers short and practical.schedules/morning.yml
cron: "0 7 * * *"
timezone: UTC
message: |
Fetch today's weather for configured
cities and post the morning brief.Batteries included
Durable sessions, schedules, Tool Bridge, human-in-the-loop — delivered as gem + Cloud for Rails teams.
Checkpointed runs on Rails Agents Cloud. Agents park between turns, survive deploys, and resume on delivery.
schedules/morning.yml becomes cloud cron after deploy — no Render workers for your daily weather brief.
Signed callbacks into your Rails models, jobs, and services. Secrets never leave your app process.
Approval-sensitive tools can park a session until a human confirms — then resume from the same durable run.
Status, environment, last run, and log lines at agents.meerkatagents.com after rails-agents deploy.
Free to sign up and define agents. Prepaid Credits before hosted runs. No pretend “free LLM” tokens.
Architecture
Durable execution and Tool Bridge on the left. Where the agent shows up — API, cron, CLI, dashboard — on the right.
Runtime
Durable execution, state persistence, event streaming
Checkpointed steps, park between messages, resume on delivery.
Rails Agents CloudModel calls, streaming, prepaid Credits metering.
AI GatewaySigned callbacks into your Rails app. Secrets stay in Rails.
HMAC /rails_agentsCron from schedules/morning.yml — no Render workers.
CronRails tools, child agents, optional skills.
Surface
Where your agent gets surfaced
Hosted at agents.meerkatagents.com
Works natively with Rails
Install the gem, mount the Tool Bridge, keep API keys and DB access in Rails. The cloud agent calls back with HMAC — no second stack.
Gemfile
gem "rails-agent-stack"Then
bin/rails g rails_agents:install
# open /agents on your domain
rails-agents new weather
rails-agents deploy weatherNot another chat gem
You want a multimodal LLM SDK, embeddings, and chat persistence you host yourself.
You need Eve-style durable agents in Rails — directory in, deploy out, schedules and Tool Bridge included.
Docs, gem, and Cloud — one path from instructions.md to production.