The writer describes using ordinary ChatGPT conversations as a practical software-development agent pool, despite not using Codex. Custom MCP servers on a Windows computer and a VPS exposed file access, code editing, terminal commands, tests, and computer-use tools. OpenAI’s Secure MCP Tunnel connected those local capabilities to ChatGPT without requiring separate inference spending or custom cloud infrastructure. The writer also modified open-source tools so screenshots could appear directly in chats, tool results were more reliable, and a dashboard could monitor the tunnel, system resources, and tool activity.
For larger projects, a stronger model planned the work and divided it into scoped GitHub issues with requirements and acceptance criteria. Multiple separate chats then tackled different issues in parallel using shared access to the same tools, while premium-model usage was reserved for planning and difficult reviews. The approach worked well for clearly defined tasks, though agents sometimes needed coordination or help from a stronger model. OpenAI’s announced changes will end the effectively unlimited chats the writer relied on and combine chat usage with Codex limits. The writer says the setup used features and tools OpenAI provided, not rule-breaking, and does not seriously believe it caused the policy change. Still, unlimited access was the main reason for maintaining an OpenAI subscription; the writer plans to switch to Claude, preferring its Opus model and finding its subscription more useful.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.