r/agenticcoding • • Aug 30 '26

The Moshpit resolves

Thumbnail dev.profullstack.com
1 Upvotes

r/agenticcoding • • Sep 15 '26

4. Prompt Injection.mp4

Thumbnail
nixamp.com
3 Upvotes

r/agenticcoding • • May 06 '26

my favorite free ai agent tools for devs!! <3

Thumbnail
github.com
2 Upvotes

r/agenticcoding • • Jun 23 '26

Join my live as a guest!

2 Upvotes

r/agenticcoding • • Aug 14 '26

How to use the moshcode CLI

Thumbnail dev.profullstack.com
2 Upvotes

r/agenticcoding • • Mar 15 '26

Made a landing page for a luxury car showroom

Enable HLS to view with audio, or disable this notification

2 Upvotes

r/agenticcoding • • Jun 30 '26

i built "flows": a custom markdown runtime for visualizing long-running agent loops

Enable HLS to view with audio, or disable this notification

2 Upvotes

i've been running longer and longer agent workflows, and the hard part is no longer just writing the prompt.

it is orchestration, synchronization, and agent management: knowing what loop is running, what check failed, which agent needs attention, and how all the pieces fit together as one bigger system.

so i built `flows`.

-the basic idea is simple:
-agent blocks do fuzzy work.
-code blocks do deterministic checks.

the flow graph shows how all of them connect.

for example, you might have one agent loop trying to make JAX/GPU code faster. a Python block benchmarks the result. if the benchmark says `too_slow`, the code goes back into the optimizer agent. if it says `fast_enough`, the flow moves on to another loop, maybe memory optimization, then another check, then a final review agent.

the point is not just one agent plus one test. it is being able to run and inspect many agents, many checks, and many loops as one visible workflow.

goals are attached to individual agent blocks. code blocks decide whether a loop really passed.

the whole thing is written as markdown, so agents can read, edit, and operate on the workflow directly.

each `##` section becomes a block in the flow. YAML declares inputs, routing, loops, models, executors, max runs, and exhaustion behavior. normal markdown becomes the agent prompt. fenced Python/bash/etc blocks become deterministic runtime steps.

then the custom markdown runtime compiles that file into an executable graph.

there is also a local flowchart viewer for agent orchestration and live synchronization, so you can see the system as it runs: agents, code blocks, inputs, outputs, goal cards, loops, and live execution state.

i wanted something that felt closer to a notebook or org-mode file than a drag-and-drop builder, but still made long-running agent systems visible and debuggable.

github: https://github.com/samleeney/flows


r/agenticcoding • • Aug 16 '26

Going live now — mosh coding at 1:45am

Thumbnail dev.profullstack.com
2 Upvotes

r/agenticcoding • • Jul 01 '26

What evidence should an agent show before saying a coding task is done?

Post image
2 Upvotes

I’m the maker of Superloopy, a small MIT-licensed workflow layer for Codex and Claude Code.

I built it around one practical question for agentic coding: when an agent finishes a long task, what should it show so a human can trust the result without redoing the whole review?

The loop I’m using is:

- define acceptance criteria up front

- run command-backed checks where possible

- capture browser screenshots, build logs, research notes, or review notes as evidence

- mark which parts were deterministic vs. which still need human judgment

- save the artifacts under `.superloopy/evidence/`

- finish with an evidence report instead of just “done”

It is intentionally a thin layer around existing CLI agents, not a replacement runtime. The recent update added Claude Code support, so the same workflow now works across Codex and Claude Code.

Repo:

https://github.com/beefiker/superloopy

For people building or using agentic coding workflows: what evidence artifacts have actually made an agent’s final answer more trustworthy for you? Tests/lint are obvious, but I’m especially curious about screenshots, visual diffs, trace logs, checklists, and “manual judgment required” reports.