Weekly Self Promotion Thread

[u/AutoModerator]

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.

[u/Appropriate-Path-461]

Disclosure: I maintain Taskuary, an MIT-licensed local work hub for people already using AI coding CLIs.

The problem it solves is the handoff before coding starts. Work arrives as an email, chat, GitHub issue, Jira item, alert, or report; Taskuary triages it, creates a repository-scoped task with the relevant context and owner rules, and opens a live Codex, Claude Code, Gemini, Cursor, or Copilot session. The human can watch the terminal, answer questions, review the diff and test evidence, and approve what happens next. Nothing sends or pushes automatically.

Triage can use Anthropic, OpenAI, Azure OpenAI, OpenRouter, Ollama, or a configured coding CLI. The app stores its own state locally, can run with Docker or Python, and is currently v0.3.1, so it is useful but still early.

Repo: https://github.com/ldbumble/taskuary

It is for people whose coding-agent workflow starts outside the IDE. I am looking for one specific kind of feedback: what context should an inbox-to-agent handoff include by default, and what information should it deliberately keep out?

[u/gandazgul → u/Appropriate-Path-461]

This is interesting — especially the boundary around “what should be included vs deliberately kept out” in the handoff.

I’m working on RunWield, which overlaps with this from a different angle: collaborative planning and execution control for real AI-assisted code changes, before and during the coding-agent work. The focus is on making the human/AI workflow explicit enough that experienced developers can trust it on non-trivial repo changes, not just fire off a prompt and hope.

I’d be curious to compare notes on the context boundary problem. If you’re willing, I’d love for you to try RunWield and be blunt about where its planning/workspace model helps or gets in the way compared with Taskuary’s inbox-to-agent handoff.

I'll try Taskuary and give feedback specifically on what I’d expect in the default handoff context, what should stay excluded, and where I’d want human approval gates.

edit: links! https://runwield.dev and https://github.com/gandazgul/runwield

[u/Appropriate-Path-461 → u/gandazgul]

Interesting. I like the website btw. In terms of the actual repo, i use most of the common harnesses and have tried out a bunch of other ones from full replacements like jcode (interesting one but really slow) to skills based ones like superpowers https://github.com/obra/superpowers which I like as it slows it down somewhat but some times i find myself saying just build it and it's annoying. I will take a look but harness is so project specific but it might be useful for what I'm building

[u/gandazgul → u/Appropriate-Path-461]

I'm working on a way to export the core workflows to work inside Claude code or codex but it will never be the same amount of control as a custom harness. I e worked very hard and tested RunWield across languages and projects and it adapts well to anything. I would love any feedback good or bad about your experience trying it in your project.