Just because Claude hacked together a panel on top of Jira doesn't make it a scalable pattern. Most of these on-the-fly generated UIs are slow as hell, hijack native page events, and leak memory like crazy. It's fine for a personal PoC, but rolling this out to an entire team is pure insanity

• xp84

  today at 3:43 PM

  As though Jira itself is a model of well-architected and performant frontend!

This resonates so much. We’ve spent years automating the 'coding' part, but the 'process' part is still stuck in a click-heavy 2010s workflow. I don't want an AI that writes boilerplate; I want an AI that observes my Git commits and Slack discussions, then automatically updates the ticket status, linked PRs, and documentation. The real productivity killer in 2026 isn't the lack of code assistants, it's the 'administrative tax' of keeping project management tools in sync with reality

• KurSix

  today at 2:15 PM

  Dumping a continuous firehose of Slack messages into an LLM context is a guaranteed way to bankrupt the company. Plus, the latency is a joke: by the time the agent parses the thread and hits the Jira API, you could've manually dragged the tickets across the board three times over yourself

  • AnimalMuppet

    today at 3:11 PM

    I don't need lower latency. I need to not have to do it myself.

    For that to work, though, I also need to not have to check it myself. The tool has to be reliable.

I vibe-coded my own Jira interface at work. Everyone likes it better and half the company is using it now lol.

• niel_hu

  today at 3:26 PM

  Curious about your approach. How did you implemented it ? how did it talk to Jira backend ?

It's definitely part of the SaaS-apocalypse story. LLMs shine at making little programs that integrate with an existing API to do some small task. Management has always overestimated the effort to develop that kind of thing and underestiamted the effort to develop applications with GUIs because... user interfaces are the Vietnam of computer science.

The greatest danger of the current time is that the likes of Salesforce and LinkedIn who have something interesting behind an API or web site try to lock down access so instead of using competitive high-quality AI agents we're stuck with the brain damaged AI agents they want to force on us.

• niel_hu

  yesterday at 4:35 PM

  Yeah, totally agree. But I don't think they can keep it locked down any more, with the rise of computer use agents, the boundary between interfaces designed for humans and those designed for computers is becoming increasingly blurred.

  • KurSix

    today at 2:19 PM

    Cloudflare and Datadog are already training models to detect agent-like mouse movements and DOM interactions. They'll lock this down easily, and we'll just end up in an ML vs ML arms race. It's still way too easy to fingerprint a script vs a real human just by looking at input latency patterns tbh

  • PaulHoule

    yesterday at 4:48 PM

    Last year I was talking with somebody about business plans and we were talking about using browser extensions for social news applications to get around paywalls, another part of the "lockdown economy".

    I have an "image sorter" that ingests image galleries, it used to use a bookmarklet that cued a webcrawler but after a decade of having my time as a user wasted clicking on those Cloudflare thingies I finally had it get in the way of my webcrawler.

    I was talking about options w/ Junie and it suggested, "why not write a browser extension?" and I'm like "is that hard?" and it says "no" and 20 minutes later I have a prototype browser extension.

    So that plug-in you're talking about where an AI can see directly into your browser is another option, another is vibe-coding a custom browser extension. I think it was always pretty easy to write a browser extension but I had I done it myself my usual scholarly way I'd spend a few hours reading documentation before I started coding and never realized just how simple it is... Just the way people are discovering web crawlers and API integrations are easier than they thought.

    • OkayPhysicist

      yesterday at 5:02 PM

      There really isn't hours worth of material to put together a browser extension. You can read all the relevant docs in tops an hour, but you can follow the MDN tutorial on it to get the "inject some Javascript into pages with a url matching this pattern" level in less than 10 minutes.

      • KurSix

        today at 2:21 PM

        Yeah, logging "Hello World" from a content script takes 10 minutes. But then you run into Manifest V3 service worker lifecycles, bypassing CSP on the host page, and syncing state across tabs, and suddenly your "quick one-hour project" turns into a completely burned weekend

      • skydhash

        yesterday at 6:37 PM

        Also most extensions are open sources. You can hack something from just glancing at the code of some samples.

Did you create a new extension or a custom script for an existing one?

• niel_hu

  yesterday at 5:55 PM

  Neither. I asked claude through extension to modify the page directly

Rovo is sad you never pick it for these kinds of things

• niel_hu

  yesterday at 5:39 PM

  Rovo from atlassian? no thanks.