Glenn 'devalias' Grant

See also: - https://github.com/jehna/humanify/issues/8 - https://github.com/jehna/humanify/issues/20

> Unfortunately there's not that good rate limit throttling/retry logic built into Humanify yet. > Added some thoughts about parallelism to issue #167 See also: - https://github.com/jehna/humanify/issues/2 - https://github.com/jehna/humanify/issues/139

> I suppose the best solution could be that Humanify would retry with a prompt like: > > ``` > Rename a function ..., here is a list of names...

Related context (from secondary comment on another issue): > Also it can happen that a variable gets renamed but another one with the same name already exists in the scope,...

@neoOpus From a quick skim through your comment, it seems like it might be better positioned in a new issue, since it sounds more 'standalone'; rather than on this one...

> probably better if you create a new issue with that comment and can discuss thoughts there more as appropriate @neoOpus I made the following issue for it and copied...

Most directly interesting/relevant here from the recent OpenAI announcements is probably the Codex SDK: - https://developers.openai.com/codex/sdk/ - > Codex SDK - > Programmatically control local Codex agents But the Agent...

> > Since then, the AI landscape has evolved dramatically, making my original, out‑of‑scope ambitions more attainable. I now believe that developing an MCP for HumanifyJS is essential, and that...

> `process.stdout.cursorTo` is only defined when the shell you're running in isn't capturing the output. You need to check `process.stdout.isTTY` before trying to access it. - https://nodejs.org/api/process.html#a-note-on-process-io - > To...

Since this issue is still valid, and I don't have the access to re-open it based on @ItsHarper 's findings/contribution; I created a new issue to track the ongoing bug,...