A Hacker News discussion kicked off this week with a deceptively simple question: where should AI coding agents live? The thread, now sitting at modest engagement levels, reflects a growing conversation among developers trying to figure out how agentic workflows will reshape their daily toolkit.

The Editor vs. IDE Debate

The original poster asked about experiences with AI agents running directly in editor terminals (think VS Code's integrated terminal) versus full IDE integrations like Cursor, which has baked agent capabilities into its core editing experience. It's the kind of question that seems technical on the surface but touches something deeper—who owns the development environment going forward? One commenter cut through the noise with a pragmatic take: different tools will serve different purposes, and they'll likely all connect to the same underlying agents and information sources.

Why GitHub Might Win Anyway

Here's where it gets interesting. Rather than debating VS Code versus Cursor, one HN contributor floated a more provocative prediction: Jira, Bitbucket, and GitHub itself may become the primary interface for agentic development. The reasoning is sound—agents handle the code generation in the background while humans review stories, plans, test outputs, diffs, and pull requests through familiar project management tooling. This shifts the developer persona from hands-on coder to reviewer and orchestrator.

The Management Layer Takes Over

The commenter pointed out something crucial: if agents handle the grunt work, developers naturally migrate toward management tools and user-facing or business-side interfaces. Those stakeholders—product managers, executives, clients—won't adopt a two-tool solution like VS Code plus Cursor. They'll live in Jira and GitHub's web interfaces. This suggests that the real agent revolution might happen above the editor layer rather than within it.

Key Takeaways

  • AI agents will likely connect to multiple interfaces simultaneously, not dominate just one
  • Project management platforms (Jira, GitHub) may become primary human-agent interaction points
  • Developer workflows shift from writing code to reviewing and orchestrating agent outputs
  • Business stakeholders already live in these tools—agents will need to meet them there

The Bottom Line

The VS Code versus Cursor debate feels like arguing about which horse-drawn carriage has better leather seats while the automobile gets built elsewhere. The real action is in platform-level integrations where agents become invisible infrastructure and developers become high-level reviewers rather than line-by-line coders.