Project

Roadmap

What is being built next, and what is deliberately out of scope.

Next

Scheduled missions

modem schedule "every morning" "…". A mission is a job with a trigger, and the trigger lives in the cloud: that is the whole point, since your laptop is shut. Setup stays interactive: build and debug the task with an agent, then schedule it, and the same environment runs it.

Talking to a detached agent

modem tell "also check the Safari case", sending a message to a running session without reattaching to it.

Notifications

An email when a job finishes, fails, or opens a pull request. Fire-and-forget is only half a feature without the moment it comes back to you.

Later

  • Workspaces: several projects on one computer, each with its own scoped secrets and missions.
  • Team computers: shared machines, team secrets, roles, audit.
  • Event triggers: a new pull request, a new file, an incoming email.
  • More agents as first-class citizens: an adapter is a small thing.

Deliberately out of scope

  • Public ports and always-on hosting: a computer is a workbench, not a server.
  • GPUs and training workloads.
  • Reselling inference: your tokens stay on your own account.
  • A Modem agent of our own. We run yours.
◗

Something missing that would change how you work? Tell us, during the alpha the roadmap is genuinely shaped by the handful of people using it: dom@fabriquestudio.fr.