That would be glorious! If ChatGPT doesn't get the permissions right on the first try I know that I'm going to have to spend the next hours reading the documentation or trying random combinations to get a token that works.
replyWhy is "on the first try" so important? What's wrong with telling it your end goal and letting it figure out the exact right combo while you go off and work on something else?
replyBecause I don’t want the earth to melt. Maybe if we’re all a bit more efficient we can postpone our doom for a bit.
replyThat's also my experience. If it does not work on the first try, the model will likely continue to struggle with the problem, unless I babysit it.
replySo I prefer to dig through the source of truth, which also helps me build my mental model around the problem.
A doctor command that does this is always nice! Wish more services would have this
replyI would second this. Would be very helpful. Had a fat finger issue a while ago that this would have saved.
replyMaybe even better: create that key for you.
replyI think this boils down to more discoverability of the entire API. While I'm not a fan of GraphQL necessarily, it does provide the tools for very robust LLM usage typically because of the discoverability and HATEOAS aspects they actually follow compared to most "REST" APIs. I would love if LLMs could learn everything they need to about an API just by following links from its root entry point. That drastically cuts down on the "ingested knowledge" and documentation reads (of the wrong version) it needs to perform. Outdated documentation can often be worse than no documentation if the tool has the capability of helping you "discover" its features and capabilities.
reply