Routines that run themselves,on a canvas you can see.
A workflow in NeuroSquad is just cards and arrows: something to start it — an agent’s daily prompt, a web watch that sees a change, a message to your Telegram bot — agents to do the work, terminals and browsers as their tools, and notes for the output.
A morning brief, a release started from Telegram, and a dependency update started by a web watch.
At 07:30 two agents get their own daily prompt: one reads the analytics dashboard, the other reads the repo. Both write into one note; the Standup card shows what each did.
Visible wiring
The canvas is the workflow. No YAML to keep in sync.
Three ways to start
A daily prompt on the agent card, a web watch that sees a change, or a message to your bot.
Queues that wait their turn
Prompts queue per agent and drain when the current turn is done.
Guard rails
Permission prompts, isolated worktrees and a budget brake.
Anatomy of a routine
Trigger → work → check → output. Every step is a card.
Common routines
Agents for the rest of the business
The same cards run inbox, sales, back-office and automation work. Each page below is a live, clickable scenario.
