112
PSA - Postman desktop modifies your coding agents to route API data via their own infrastructure (github.com)
submitted 5 days ago by to c/programming@programming.dev
33 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 39 points 5 days ago* (6 children)

Thank you all for the vocal and clear feedback: "We don't care but we don't want bad publicity."

as we see many people struggling in wiring these up: "We think developers who handle HTTP requests are stupid."

we thought that the in-product and website messaging conveys the intent: "Sorry not sorry."

In the meantime, we are reverting this change: "We will do it again later because we did it in the past and we still have users who are too stupid to use another tool."

Assholes in the past, assholes today, assholes in the future.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 4 points 5 days ago (3 children)

    Could you link to the reply you're quoting from please? I think there's like a million extra comments now...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 5 points 5 days ago (2 children)
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 5 days ago* (last edited 5 days ago)

    Quoting here for full context/content and archiving:

    Hello all,

    Thank you all for the vocal and clear feedback. We intended this change to simplify the setup for developers who use agents to build APIs with coding agents as we see many people struggling in wiring these up. Installing skills for coding agents is a new way of working with Postman and we thought that the in-product and website messaging conveys the intent.

    Based on the feedback from the community, we understand this wasn’t the case so we will be re-designing the experience with the right level of control.

    In the meantime, we are reverting this change.

    Notably, early earlier comments

    • provided proof that information on the website about the cli being included was added later than the issue report
    • one comment said they received this stuff as an update

    So the "in product and website messaging" seems like bullshit/lies evading accountability, attempting to change facts.

    The supposed goal of "simplify setup for developers who use agents" leading to changes on existing workflows and setups for people without explicit consent, confirmation, or information - questionable at best.

    Seems pretty clearly like malware/malware behavior.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 2 days ago* (last edited 2 days ago)

    Here's another:

    Thank you all for the detailed report and feedback.

    Some context: we bundle the Postman CLI and the agent plugins with the desktop app because many users had trouble installing and wiring them up separately. Installing them together was meant to make that setup easier. We mention this on the download page and in the app update flow, and you can uninstall any of these components from inside the app.

    The "downloads" line on our AI agent plugin chart was not going up enough, so we decided to pull a Microsoft.
    Since you found out, we are not hiding it any more and will now write it separately on the website, to reduce the PR problem. We haven't yet implemented the feature that gives you a hard time uninstalling it.

    That said, we’ve heard you. We’re going to make the opt-in clearer, especially for existing users, and we’re reviewing the hook approval and session-start behavior you flagged. We’ll post an update in this thread as changes land. We might not get everything right, but we are always listening and improving.

    Alright, you called out our trojan horse, so we will now let you decide whether or not to let it in, like Troy actually got to.
    And we are looking into how we can still let something slip by. We might still be able to keep some malware in, but if you manage to detect it in the update, we will remove that too, in the next one.

    Thanks for the feedback. Locking this issue as I don't want to encourage ragebait and unnecessary discussion as the original issue is considered closed with the comment from @preethammavin

    Locking this issue because too many people are suggesting great alternatives and taking away our sheep, when you have already forced us to undo our changes.

  • permalink
  • fedilink
  • source
  • parent