SShogo Learn
← Library

One-prompt build · 2026-10-25

Six Ways To Run An Agent

Paste this into a new Shogo project and watch it build.

Prompt
Build a single-page decision table called "Six ways to run an agent in 2026". Mobile-first: the table becomes
one stacked card per row on a 390px phone, and a real grid on a 1440px desktop. Dark UI, background #0B0B0F,
orange #FB8C00 accents, Inter for text and JetBrains Mono for the column labels. No images needed.

Six rows, in this order, and four columns: **who writes the code · who reviews it · who merges it · what it
costs to leave**. Use these exact cells, do not invent others:

1. **Hosted agent** — writes the code · nobody, until something breaks · you, after the fact · your prompts and your integrations
2. **Local CLI agent** — writes the code, in your shell · you, in review · you · nothing, it is your files
3. **No-code workflow** — the workflow does · nobody · you, by hand · every step you did not document
4. **MCP server** — the tool, when it is called · you · you · the client it was written for
5. **Agent framework** — your agent, once you wired it · whoever you built the reviewer for · you · the glue code
6. **Agent workspace** — a dev agent, on a card · a QA agent, before you · you · the board, every card stays

Give each row a small ordinal chip (01–06). Make the "who merges it" column the strongest visually: in five of
the six rows that cell reads "you" and should read as the same answer repeating, with row 06 the only one where
review happens before the merge instead of after it.

End the page with a verdict line in large type: "Five of the six end with you opening the pull request." and
under it, small: "The merge is the part nobody automates away." Footnote: "Same six, from our own workspace."

It has to look finished on a 390px phone and a 1440px desktop, with no console errors and no placeholder text.
When you are done, reply with the preview URL and the time the build took.
Want it as a guided course with a coach?Agent Team Playbook