Marty
Marty is an AI-Agent Sandbox containing a master agent that runs on a centralized server, using Supabase to store widgets and agent-created backend files.
Core trick
A central agent server stores user-generated widgets and backend files in Supabase, so non-technical users run agents without local hosting.
Description
Marty is an AI-Agent Sandbox containing a master agent that runs on a centralized server, using Supabase to store widgets and agent-created backend files. Users can configure context, adjust skill permissions, and set up autonomous event activations to custom tasks all from just the website. With a familiar chat interface and simple conversations, users with no technical expertise can create any tool or workflow they can imagine, build their dream workspace, and set up an autonomous agent without ever hosting anything on their own devices or exposing their filesystems. Marty removes the learning curve to Opus entirely by making it completely frictionless, providing an intuitive and extremely accessible platform for people who want an agent that just works.
Project Website is at: https://rasbpi.changsean.me/landing
Demo Code: InIoNbzXyAcq2Z9Gvx5sGCd+v1P9kFum01Op9UmQwI4=
README excerpt
# marty <img width="970" height="571" alt="Screenshot 2026-04-19 at 2 34 51 PM" src="https://github.com/user-attachments/assets/7834ca7d-e524-4e80-8072-79c361c05e0e" /> **An AI agent sandbox for everyone — not just engineers.** marty (formerly *dyno* on days 1–3) is a dashboard-first environment for running, observing, and collaborating with a personal AI agent. It turns the command-line surface area of modern agent frameworks into a visual canvas of composable widgets, so non-technical users can direct real work — research, trading, file management, browsing, code execution — without ever touching a terminal. --- ## Why marty Agent tooling today assumes the user is a developer: shell prompts, config files, JSON blobs, scattered logs. Most people who would benefit from a personal agent are locked out by that interface. marty closes the gap with three commitments:rface the agent acts on. - **One simple chatbox, many Mini Marties.** Users type into a single plain chat input. Behind it, marty orchestrates a fleet of **Mini Marties** — specialized sub-agents bound to individual widgets — that the main agent dispatches, supervises, and stitches back into one coherent answer. --- ## Memory state marty treats memory as a visible, editable part of the interface rather than a hidden prompt-engineering detail. - **Persistent memory store.** Memories survive across sessions and are scoped to the user, stored behind `/api/memories` and surfaced through the `MemoryWidget` on the