The Rush Method
Practices for the Agent OS era.
Rush is opinionated about what agents are, how they should work, and what a trustworthy interface should feel like. These principles are the operating assumptions behind the product and the site.
Foundations
The premise behind Rush: agents are not better chat tabs. They are a new operating layer for work, memory, and coordination.
Why agents, not chatbots
Chat is good for intent capture. It is weak at multi-step work, handoffs, and durable output.
Rush treats chat as the front door, not the product. The product is work that continues after the prompt.
The memory model
Useful agents need memory at more than one level: the person, the task, and the artifact itself.
Rush keeps continuity across sessions so the system can pick up where the work left off.
Real work, not chat
Rush is built around outcomes you can open, share, and act on — not clever turns of phrase inside a window.
Artifacts make the work legible. They also make it portable.
Discipline
Taste is not ornament. It is a product decision. The site and the product should make one clear claim at a time and prove it with something real.
One claim per surface
Every screen, section, and page should make one argument cleanly instead of stacking five weak ones.
Clarity compounds. Accumulated claims do not.
Show, don't promise
If a real artifact, screenshot, or output exists, it should replace descriptive marketing copy.
Proof beats positioning when the category is still being earned.
Restraint over noise
Premium products feel deliberate. They do not beg for attention on every line.
Rush uses editorial discipline as a trust signal.
The product
Rush is not one more wrapper around a model. It is a local-first runtime, a marketplace, and an interface layer shaped around agent work.
The container model
Agents should be installable, composable units with clear boundaries, not one giant assistant doing everything badly.
Rush treats agents more like apps than prompts.
Local-first runtime
Important work feels better when the user can see, steer, and contain it on their own machine.
Native access is a product advantage, not just a technical preference.
The artifact loop
Work compounds when outputs can be refined, shared, and handed to the next agent without starting over.
Artifacts are the connective tissue between sessions, people, and agents.