Is anyone experimenting with different ways of using LLMs for coding?

I'm a bit annoyed by the feeling that we're kind of stuck when it comes to using LLMs for programming.I use Claude Code and Codex, but I haven't been able to enter flow state like I can when I hand write code.This is kind of ironic to me since AI should be a bicycle for the mind, but right now it feels like a bicycle that just brakes abruptly every couple minutes. I stop, wait, review, prompt again.Is there anyone exploring something fundamentally different than the prompt response loop we have today?I actually think the idea of a tab model is directionally better than prompt response.Would love to hear about any startups, personal experiments, etc.

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

62

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

Build developer tools that replace the stop-start prompt-response loop with continuous, flowing LLM-assisted coding.

The pain

Developers lose flow state when using Claude/Codex because they must stop writing, wait for generation, review output, and re-prompt repeatedly. This friction negates the productivity gains LLMs should provide. The current UX treats coding like a Q&A session rather than a collaborative writing process.

The gap

No mainstream tool has solved the interaction model problem. Tab-based or streaming approaches exist in fragments (Cursor, GitHub Copilot's inline suggestions) but none fully eliminate the cognitive switching cost. The market is still optimizing within the prompt-response paradigm rather than reimagining it.

Build angle

Create an IDE plugin or standalone editor where LLMs work in parallel with the developer, suggesting next lines, completing functions, or refactoring sections without requiring explicit prompts. Use streaming, predictive generation, and context windows to keep the developer in flow. Start with a specific language (Python/TypeScript) and measure flow-state metrics (time between interruptions, lines written per session).

Strengths

  • Clear, articulate pain point from experienced developers (not hypothetical)
  • Identifies a real UX/interaction design problem, not just a capability gap
  • Tab model and streaming are technically feasible with current LLMs
  • Developer tools have strong unit economics and low churn if they work
  • Founder frustration often signals genuine market need

Risks

  • Vague on what 'flow state' actually means, needs quantifiable metrics to validate
  • Cursor and Copilot already own significant mindshare; differentiation unclear
  • LLM latency and hallucination rates may make continuous suggestions annoying rather than helpful
  • Requires deep IDE integration; distribution is harder than web apps
  • May be a preference/workflow issue for this founder rather than a market-wide problem

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Is anyone experimenting with different ways of using LLMs for coding?”.

Open FlyBot