Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Async – Claude code and Linear and GitHub PRs in one opinionated tool

github.com

Post reply on HN
Print view View original

11–20 of 49 posts

Re: Show HN: Async – Claude code and Linear and GitHub PRs in one opinionated tool

#11

Post by JoshPurtell »

wjsekfghks wrote: post #7
JoshPurtell wrote: post #6

Something I'd consider a game-changer would be making it really easy to kick off multiple claude instances to tackle a large researched task and then to view the results and collect them into a final research document. IME no matter how well I prompt, a single claude/codex will never get a successful implementation of a significant feature single-shot. However, what does work is having 5 Claudes try it, reading the c…

Interesting. So, do you just start multiple instances of Claude Code and ask the same prompt on all of them? Manually cherry picking from 5 different worktrees sounds complicated. Will see what I can do :)

Yeah, exactly, same prompt.

I agree, it's more complex. But, I feel like the potential with a claude code wrapper is precisely in enabling workflows that are a pain to self-implement but nonetheless are incredibly powerful

Re: Show HN: Async – Claude code and Linear and GitHub PRs in one opinionated tool

#14

Post by chis »

Great pitch, you've articulated the pain point super well and I agree with it.

I have personally had no luck with prompting models to ask me clarifying questions. They just never seem to think of the key questions, just asking random shit to "show" that they planned ahead. And they also never manage to pause halfway through when it gets tough and ask for further planning.

My question is how well you feel it actually works today with your tool.

Re: Show HN: Async – Claude code and Linear and GitHub PRs in one opinionated tool

#15

Post by wjsekfghks »

chis wrote: post #14

Great pitch, you've articulated the pain point super well and I agree with it. I have personally had no luck with prompting models to ask me clarifying questions. They just never seem to think of the key questions, just asking random shit to "show" that they planned ahead. And they also never manage to pause halfway through when it gets tough and ask for further planning. My question is how well you feel it actually…

Honestly, it's not there yet and I'm iterating to making it better and consistent. But, I've had a few moments where it got questions and implementations right and it felt magical. So, wanted to share it with more people and see how people like the approach.

Re: Show HN: Async – Claude code and Linear and GitHub PRs in one opinionated tool

#18

Post by pjm331 »

Very cool! I’ve been building an internal tool at work that’s very similar but primarily focused on automatically triaging bugs and tech support issues, with MCP tools to query logs, search for errors in bugsnag, query the db etc. also using linear for issue tracking. They’ve been launching some cool stuff for agent integrations.

And sorry I’m a light mode fan

Re: Show HN: Async – Claude code and Linear and GitHub PRs in one opinionated tool

#19

Post by wjsekfghks »

pjm331 wrote: post #18

Very cool! I’ve been building an internal tool at work that’s very similar but primarily focused on automatically triaging bugs and tech support issues, with MCP tools to query logs, search for errors in bugsnag, query the db etc. also using linear for issue tracking. They’ve been launching some cool stuff for agent integrations. And sorry I’m a light mode fan

Nice, are you building a linear app? I saw their recent post about integrating cursor, devin, etc into their platform.

And, light mode? I'm sorry, we can't be friends anymore

Re: Show HN: Async – Claude code and Linear and GitHub PRs in one opinionated tool

#20

Post by _1tem »

I've been planning to build something like this for a while now (just for myself). Love the planning workflow, will likely steal that idea.

But code review is more than just reviewing diffs. I need to test the code by actually building and running it. How does that critical step fit in to this workflow? If the async runner stops after it finishes writing code, do I then need to download the PR to my machine, install dependencies, etc. to test it? Major flow blocker for me, defeats the entire purpose of such a tool.

I was planning to build always-on devcontainers on a baremetal server. So after Claude Code does its thing, I have a live, running version of my app to test alongside the diffs. Sort of like Netlify/Vercel branch deploys, but with a full stack container.

Claude Code also works far better in an agentic loop when it can self-heal by running tests, executing one-off terminal commands, tailing logs, and querying the database. I need to do this anyway. For me, a mobile async coding workflow needs to have a container running with a mobile-friendly SSH terminal, database viewer, logs viewer, lightweight editor with live preview, and a test runner. Diffs just don't cut it for me.

I do believe that before 2025 is over we will achieve the dream of doing real software engineering on mobile. I was planning to build it myself anyway.

Post reply on HN