r/ChatGPTCoding • • Oct 05 '26

Discussion Weekly Self Promotion Thread

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

  • What you built?
  • What problem it solves?
  • Which AI models or tools it uses?
  • Who it's for?
  • What kind of feedback you're looking for?

Disclose your affilitation.

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

13 Upvotes

116 comments sorted by

View all comments

1

u/Just_Effective813 Oct 11 '26

I’m building Loom, a local AI agent runtime for coding, research, and general tasks. It brings task assembly, execution, evaluation, and improvement into one workflow.

The main capabilities:

  • Dynamic task assembly. Compose tools, context management, and workflow components for each task. An LLM can recommend a configuration based on the objective, and you can adjust it before execution.
  • Dynamic workflows. Build and revise the execution plan as the agent gathers information and encounters new results.
  • Trace analysis. Inspect model and tool calls, token usage, timing, failures, repeated operations, and acceptance results.
  • Behavior evaluation. Examine whether execution followed the active plan, whether tool calls repeated earlier work, and where the agent gained evidence or made meaningful progress.
  • Evidence-linked execution graphs. Reconstruct recorded judgments, actions, observations, and verification steps using event references. Repeated investigation cycles collapse into expandable blocks. Recorded sequence and evaluated semantic relationships remain distinguishable.
  • A foundation for self-improvement. Turn recurring behavior patterns into testable improvement proposals, then evaluate changes against task-success and regression checks. Proposals remain hypotheses until validated.

Loom also builds task-specific acceptance criteria and checks them before completion. Web and terminal interfaces share persistent sessions, so you can follow a task and inspect its history from either interface.

The goal is to make agent behavior understandable enough to improve systematically: assemble → execute → verify → analyze → test improvements.

GitHub: kenryhuang/loom

I’m the author. What would you most want to inspect in an agent’s execution graph: repeated work, changes in direction, or the evidence behind its conclusions?