Sometimes people see more value in a code itself, rather than in a product. I hope ai will shift that. The developer’s main goal at this point is helping people to contribute
“If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation.”
@theo i think there are an issue with ultra mode, also found similar with my setup. Currently subagents inherit parent model config. Custom subagents also not working
There's a flaw in Codex's (or should I say ChatGPT's?) subagent orchestration.
The spawn_agent tool doesn't let you choose the model or reasoning effort.
Therefore, every time 5.6 Sol Ultra spawns a subagent, you're getting another Sol Ultra instance.
That's why your quota gets drained so fast.
@thsottiaux Noticed a Codex custom-subagent issue. Session logs show spawn_agent sends only task_name; children start with agent_role: null, inherit the parent model, and ignore .agents/*.toml.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
@thsottiaux 1. comment on a plan in the same way as for a diff
2. auto generate environment config
3. review changes in a last run in a full screen mode as an option
4. allow start a new chat from an existing worktree + allow customise default worktree folder
@thsottiaux what an amazing release! small feature request: Is it possible to add a button here to open full screen review mode with a last run preset? or at least to have a shortcut for that
@thdxr @krishstwt @opencode do you have any concepts on how to make it as good as open tui experience for terminals? all existing solutions feels weird and not fit mobile screens at all
@rxmustdie So all elements on map are rendered by swift ui? How do you managed to sync their position with maps camera, I haven’t see good api to observe map camera updates in maps sdk? Or do you manually control camera of your map, so the gestures handled also by swift ui?
@VSapienti@jacobtechtavern@slizeray Isn’t according to Apple, an actor is a non-blocking API? So yep, in a simple benchmark, a lock will perform better. But in a real-world app that actively utilises threads for different tasks, it will be more efficient, since the system can plan and prioritise.
@trayhardplay@kot_leopo@RuslanLeviev@mr_AlienHoliday Есть ещё вариант, что агентство с ВК по этому направлению не работает. Но тк они являются агентом блогера, то все платежи проходят через них, а значит ВК может выходить на блогеров напрямую. Исключить эту версию из данных фбк как я понимаю сложно.