Had a very brief time to test it. It’s a good frontier-feeling model.
It’s handling subagents quite well, not the fastest one, but thorough.
“Load-bearing” language is suspiciously close to Opus/Fable.
Burned my small token quota pretty quick 😂
Michał Pierzchała
@thymikee
Principal Engineer for Open Source @callstackio. Core @reactnative Community contributor. Building @agent_device, RN Testing Library, ex-maintainer Jest
- Apex passed 1B tokens used after 48h since launch
- React Native 0.87 is just released. Huge step for 1.0. My favorites: - 2x faster source maps and less memory usage in dev server - SPM (experimental) - no deep imports (strict TS API) Also important: minCompileSdk bumped to 34
- many such cases > dev tells me @agent_device doesn't work > what's wrong? > codex using it for 10 minutes and can't fill a form > asking them to check a11y > not accessible at all > just found you a bug broI was debugging a production React Native app today, and the registration form was completely unusable through VoiceOver (and a11y APIs). one line: accessible={true} on the form wrapper. iOS collapsed 8 inputs + submit button into a single element labeled "Create your account,
- if you requested @callstackio Apex early access, check your email don’t know what’s Apex? it’s an expert model fine-tuned for React Native
