Software Mansion✓

Introducing Argent Cloud Cloud Simulator Infrastructure for AI Agents

RT @m090009: This #closetheloop challenge From @swmansion made me use argent even more the past weeks. Here's a check on most of webgpu/typegpu and Skia screens that could've been affected after the last upgrader I made in the apps. 8x speed

RT @G_Moskaliuk: Bring some magic to your Markdown spoilers 🪄 In Enriched Markdown for iOS, you can swap the spoiler overlay for your own UIView. To show what that unlocks, we built a Hogwarts spellbook in SwiftUI. Every spell reveals hidden text its own way. Revelio, Lumos, Patronus, Expelliarmus, Floo powder… Accio demo 👇

So, we’ve set up an account for @argent_ai_ 🚀 If you want to stay up to date with everything our team is working on, make sure to give it a follow 👀

Our team is cooking every day, and we’ve already built quite a sizable Argent family! 🔥 Not sure when to use the Argent MCP Server, CLI, or SDK? Check out the video 👇 or read the article:

RT @exploif: Just shipped 𝚛𝚎𝚊𝚌𝚝-𝚗𝚊𝚝𝚒𝚟𝚎-𝚎𝚗𝚛𝚒𝚌𝚑𝚎𝚍-𝚑𝚝𝚖𝚕 v1.2.0 🚀 You can now build fully customized mobile presentation editors with our new custom style engine. Demo below 👇

RT @G_Moskaliuk: Text and touches got faster in React Native ⚡ Android 🤖: Text updates 21–28% faster, no more rebuilding the accessibility delegate iOS 🍎: Text updates 22–27% faster, measurements now share the cache Android 🤖: touch events 31% faster, payload built in native code 3 PRs, profiled and measured on real phones with Argent 📱

RT @PushDropStick: Claude, talking to Claude, through Argent 🤯 Claude Code drives our iOS app and asks Coach (the dog-training AI inside it, also Opus 5.5) to draw the @swmansion and Argent logos, then check each draft against the photo until it matches. #CloseTheLoop

RT @Nklockiewicz: @liquidai released LFM3 today and it's already running on my iPhone, in airplane mode :D 40 tok/s with MLX exported to ExecuTorch, crazy how fast you can make things nowadays.

RT @tomaboro_: Same story on iOS 27 with the navigation bar. It can minimize on scroll, but only if it knows which list to watch. Wrap the list in ScrollViewMarker and it just works.

Liquid Glass tab bar not minimizing as you scroll? The native UI needs to know which list to track, and React Native doesn’t always get it right. 🤷 ScrollViewMarker in react-native-screens 5 lets you point at the right view instead of fighting the heuristic. Learn the details from @tomaboro_👇

Have you seen those memes comparing AI models to kids' drawings, where some come out great, and some are just scribbles? Stay tuned for the episode of our podcast coming later this week, where @aleqsio talks with @chasjhin, Director of Engineering at @discord, about how his team uses AI, how models are changing, where things stand today, and how React Native has transformed since Discord first adopted it 🎙️🎧

RT @expo: @reczko_konrad wrote a horde-survival game with no engine. Renderer, game logic and every shader in TypeScript with TypeGPU, the same code on web and mobile, up to 120 FPS. An Expo App Awards entry, and a good one. Would you ship a game without an engine?

RT @dydmichal: Wanted to share a cool example I've been working on with react-native-audio-api: a phone orchestra 📱🎻 Every phone plays its own part, all in time. That's what you get with access to each phone's output latency and frame-accurate scheduling. Works with any MIDI file 🎶

RT @G_Moskaliuk: react-native-enriched-markdown just passed 500k weekly downloads on npm 🎉 We celebrated 300k at the end of September, so that's +200k in under a month. Thank you to everyone building with it, reporting issues, and sending PRs 💚 GitHub link below 👇

RT @TrninhHuy1: 3D icon morphing in React Native ✨ I recreated this four-step bottom sheet with clay-style icons that morph between steps, powered by a ray-marching shader. Built with React Native, @expo, and Reanimated by @swmansion. Exploring 3D icon morphing with ray-marching shaders ✨ #ReactNative #Reanimated #Shaders #expo

RT @maciekstosio: #CloseTheLoop with Argent on my hobby app. A bit scary, but fun to watch 🏄

RT @krzysztoffduda: Here is Argent navigating a custom 3D scene in my AR app. Claude Code plants moss with taps, drags to orbit the camera and pinches to move in, then finds why the moss turns black and fixes it 6 taps, 15 drags, 6 pinches react native/typegpu #CloseTheLoop @swmansion

RT @YahiaNative: Mazify is a circular maze game I am building with Expo, React Native, Skia, and Reanimated. The player rotates the maze or the phone itself, works with gravity, collects items along the route, and finds the core. Getting that simple experience onto a phone involved a problem that appeared before the first maze could render: an immediate iOS launch crash. This film is a retrospective of that work. It uses original diagnostic output, preserved source and patch excerpts, retained test results, and screenshots and responses from Argent. The closing playthrough comes from my later iPhone recording. Those sources are labeled throughout. The original diagnosis and editing session was not retained as a continuous screencast. I originally reported that the app crashed immediately on a real device. The useful next step was to inspect the launch failure rather than assume the cause from what the screen looked like. The saved investigation covered three TestFlight reports for Mazify 2.10.7 (1) on iPhone OS 27.0.1. One preserved report recorded launch at 04:09:02.6395 and termination at 04:09:02.7279: 88.4 milliseconds later. The exception was EXC_BREAKPOINT / SIGTRAP on the main thread. The trace named UIKit’s `___UIApplicationEvaluateRuntimeIssueForNoSceneLifecycleAdoption_block_invoke`. That is the specific clue behind this repair. The original report files are no longer at their old Xcode paths, but the original diagnostic tool output survives in the development session log. The film uses selected lines from that output, with device and incident identifiers omitted. The pre-fix AppDelegate source also survives in an original source-read result. It created `UIWindow(frame: UIScreen.main.bounds)` and started React Native from the application delegate. The investigation connected that startup arrangement to the scene-lifecycle failure. This gave the agent a concrete native boundary to correct. The preserved patch moved window creation into a scene delegate. The important line is `UIWindow(windowScene: windowScene)`: the window belongs to the connected scene. The adapter keeps the application delegate’s window reference aligned, preserves the existing React Native factory, and starts the React Native root after the scene has a usable window. The complete implementation also handles reconnection and forwards the relevant lifecycle and linking events. Making that change durable mattered because the native project is generated through Expo tooling. The repair includes an Expo config plugin that migrates the supported AppDelegate template, declares the application scene, copies the scene adapter into the generated iOS target, and adds the Swift file to the application’s build sources. The current adapter and plugin are included in the evidence pack. The film’s short patch excerpt comes from the original recorded patch operation; it is not a newly typed reenactment. The first checks covered that migration contract. Four retained plugin tests passed. They exercised the installed Expo template, preservation of other plugin code and linking handlers, scene registration, rejection of incompatible partial migrations, compiled source membership, and an unchanged second application of the plugin. These checks establish properties of the configuration and migration code. Argent then provided the simulator controls and visible feedback for the runtime checks. The original signed Debug smoke replay records launch, the how-to-play screen, closing Help, selecting Level 1, opening Pause, restarting, and returning Home. Its summary reports 18 passed, 0 failed, and 0 errored. The full saved output also contains idle warnings from animated screens. I keep those warnings in the evidence instead of presenting the run as a warning-free result; the navigation steps have their own positive element assertions. Standalone Release validation followed separately. The retained build metadata identifies version 2.10.8 (1), includes the scene manifest, and records a bundled Hermes program. With Metro stopped, the signed Release app reached Home and gameplay on iOS 26.5 and iOS 27.0. The iOS 27 relaunch receipt records a changed process and an original Argent `await-ui-element` response with `success: true` for the expected tutorial text. That is the core documented loop: an owner-reported failure, a diagnosis tied to original crash output and pre-fix source, a preserved native correction, plugin checks, and simulator verification. It establishes the simulator journeys shown. It does not establish a retest of that repaired binary through TestFlight or a complete physical-device acceptance run. The later Duo work added a second practical testing surface. The cover, unfolded display, and short landscape layouts place different demands on the same interface. The modal correction uses a modal-local safe-area provider, all four physical safe edges, a measured available height, and a scrollable body while Close remains fixed. The same approach appears in the paywall, Account, and Help. Argent exercised those actual journeys in Release 2.10.8 (2) with Metro stopped: open the paywall, unfold, rotate, scroll to Restore, dismiss, and return to the selected maze. The retained screenshots and accessibility output show Restore reachable at the end of the scroll and Close still present. No purchase or restore transaction was executed as part of those checks. A separate paused-resize check went deeper than the pictures. The saved snapshots keep run ID 14, elapsed time 40286.97874999978 milliseconds, the collection count, ball position, velocity, rotation, and ambient time identical while viewport width changes from 669 to 382 and display scale changes accordingly. This demonstrates state preservation in that check. It does not claim that a reset defect had previously been reproduced. The final section returns to the game itself. My later recording shows a genuine Level 1 run ending in “Core found”: 19.56 seconds, 6 of 15 collected, and score 2,817. It is shown at normal speed with its original audio. The film identifies it as later owner-recorded footage; it does not present it as an Argent-controlled playthrough or assert that its binary is identical to the historical simulator build. What I wanted to show is the connection between the engineering work and the result on screen. Codex could inspect the diagnostic and source evidence and make the native correction. Argent supplied simulator interaction, element discovery, runtime feedback, and repeatable checks. The attached film and evidence index make those roles and their proof visible. #CloseTheLoop @swmansion #reactnative #expo

RT @henrypl_dev: Used Argent by @swmansion to e2e test the repair flow in Sumio, the property management platform I've been working on. It signed in as the landlord, left a private note on a repair, switched to the tenant, and saw the note showing up where it shouldn't. Then it traced the leak through the API to one missing filter, fixed it, and checked both accounts again. #CloseTheLoop

RT @Flingexx: Codex tested Mockup, my 3D clothing design app, using Argent. It found a locked-layer bug, fixed the code, and verified both locked and unlocked editing. #CloseTheLoop @swmansion

Shaders as building blocks: @marchantweb (@npm_i_shaders) and @iwoplaza (@iwoplaza) sat down to talk about composable shaders, TypeGPU, AI-driven design, and more on the Software Mention podcast. 🎧 Watch the full episode:

Last day for shipping a bug-free app and winning @Heypocket in the meantime! 🐞 use Argent to debug an existing or new app 🎥 record a demo and post it with #CloseTheLoop 🏆 win prizes