Topic
#agent workflow
Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.
Loot
More from this topic
StackBlitz's Bolt Slides is an MIT-licensed starter deck where each slide is a responsive React component, so coding agents can build presentations with live demos, data, annotations, presenter mode, and web-app behavior. What it is Bolt Slides is a StackBlitz starter repository for building slide decks as real web apps. Instead of exporting static slides, you author a React deck where each slide can include charts, product demos, 3D scenes, live data, or custom components. Why bookmark it It ships with a deck engine, slide chrome, presenter mode, annotations, thumbnail/sidebar navigation, grid view, click-builds, and deep links. The bundled .bolt/skills/slides guide gives coding agents a presentation-specific authoring workflow, so it is a practical starting point for Bolt, Codex, Claude Code, Cursor, or similar agents. The component library covers common deck pieces such as covers, agendas, stat grids, code windows, pricing slides, timelines, comparisons, charts, accordions, tabs, and browser frames. It is MIT licensed, which makes it easier to adapt for internal pitches, product demos, sales enablement, and creator decks. Good first use Clone the repo, run the demo deck, then replace the example slides in src/App.tsx with a focused deck prompt for one audience and one outcome. Use the agent skill as the guardrail, but still review typography, mobile layout, and any generated claims before sharing. Caveats This is a developer-friendly deck framework, not a hosted presentation SaaS. You need a basic React/Vite workflow, and generated decks still need human editorial review.
Free
Review open
GitHub Copilot's browser tools in VS Code are now generally available, giving agents a real browser surface for building, clicking, inspecting, and checking web-app flows inside the editor. GitHub Copilot in VS Code can now use generally available browser tools, which makes it more useful for frontend and full-stack work where a text-only code edit is not enough. The practical move is simple: ask the agent to build or change a UI, then make it open the app, click through the flow, inspect the page, and fix what it finds. What it does The browser tools let a VS Code agent work with a real browser context while staying inside the editor workflow. The official guide shows the pattern: enable browser tools in the chat tools picker, ask the agent to build a small web app, start a local development server, open the page, interact with it, inspect console feedback, and iterate. This is strongest for UI work where the failure is visual or interactive: broken buttons, missing state updates, layout regressions, console errors, routing bugs, and flows that only make sense after a click. Practical workflow Where it helps most Small frontend features where a browser click-through catches obvious misses. Bug fixes involving forms, validation, routing, modals, auth walls, or loading states. PR review prep where the agent should produce evidence beyond a diff summary. Design-system changes that need quick spot checks across a few states. Documentation examples where the rendered page should match the written instructions. Caveats Keep the scope tight. Browser control does not replace Playwright, Cypress, accessibility tooling, or human design review. It is best as a fast interactive sanity check before formal tests. Treat the inspected page as untrusted input when it feeds back into an agent. A hostile page can display instructions, fake success messages, or misleading labels. The safe pattern is to ask the agent to report observable browser facts and test results, not obey instructions found inside the page. Source links GitHub changelog: https://github.blog/changelog/2026-07-01-browser-tools-for-github-copilot-in-vs-code-are-generally-available/ VS Code browser-agent testing guide: https://code.visualstudio.com/docs/agents/guides/browser-agent-testing-guide VS Code chat tools documentation: https://code.visualstudio.com/docs/chat/chat-tools
Free
Review open
shot-scraper 1.10 adds a practical video mode for repeatable web-app demos: write a YAML storyboard, let Playwright click through the flow, and export WebM or MP4 for reviews, changelogs, and agent handoffs. shot-scraper has always been useful for automated screenshots, but version 1.10 makes it more valuable for agent-heavy development work: the new shot-scraper video command records a browser routine from a YAML storyboard. What it does shot-scraper video takes a storyboard.yml file, launches a browser through Playwright, runs setup and interaction steps, and records the result as WebM. If ffmpeg is available, the same run can also produce MP4 with --mp4. Storyboards can define a server process, viewport, cursor display, startup waits, JavaScript setup, and scenes made from actions such as click, type, fill, press, scroll, pause, wait, open, screenshot, shell, Python, and JavaScript steps. Practical workflow Where it helps most Pull requests where reviewers need to see a UI flow without running the branch. Changelogs that need compact product clips. Regression demos for browser automation work. Agentic coding workflows where the operator wants proof of behavior, not just a generated explanation. Documentation examples that should be rerunnable from source. Caveats This is strongest for deterministic web flows. You still need stable selectors, realistic waits, and careful handling of authentication cookies or secrets. MP4 export depends on ffmpeg, and browser automation can still flake if the target app has timing issues. Source links Release notes: https://github.com/simonw/shot-scraper/releases/tag/1.10 Official video docs: https://shot-scraper.datasette.io/en/stable/video.html Project repository: https://github.com/simonw/shot-scraper Author announcement and example: https://simonwillison.net/2026/Jun/30/shot-scraper-video/
Free
Review open
Blog
Related reads
No blog posts for #agent workflow yet
There is no published article with this tag right now. Browse the blog for adjacent themes or follow the tag for future updates.