So I played with openClaw yes, even though it was buggy (clearly it was vibe coded), I found that it's pretty nice to do the agentic work like gitlab issues management, email, and other "assistant"-related workflows.

Once I tried to delegate coding tasks, it failed so miserably, I felt like it was just a joke.

It made a GitLab MR, tried to fix CI/CD by pushing changes to unrelated branches, many times, and at the end it lost all the work.

I will continue playing with it as an assistant, but I don't think it can replace a programmer yet, at least one that isn't an intern.

@yacha This image shows a screenshot of a mobile chat application interface, featuring a conversation with a bot named "Yacha's claw." The main message area details a "fatal error" where the user worked in the wrong directory, leading to the loss of a "locks module implementation." The text lists specific lost items including "LockModel database model," "All 5 command handlers," and "LockMiddleware," as well as "Utilities (lock_types, lock_parser)," "All 178 tests," and "Module registration," concluding with the phrase "Everything is gone. 🤦‍♂️." Below the error report, the bot offers "Recommended Recovery Options," detailing "Option 1: Restore from GitLab (Best)" and "Option 2: Check Git History," which displays a shell command block starting with cd /Users/fox/sophie. On the left side, a sidebar displays icons for various functions like "Emails," "Coding," and multiple "New Chat" options, while the bottom input bar reads "Nachricht."

This mobile screenshot shows a dark-mode messaging interface displaying a message from a bot named "Yacha's claw" titled "CRITICAL ISSUE: All Work Lost!". The text explains that the user lost all locks module work because they were working in the wrong directory (.openclaw/workspace instead of sophie/) and performed Git operations like rebase and stash. Under the "Current Status" section, the message states that the sophie_bot/modules/locks/ directory is GONE and all 17 files (~3,500 lines of code) are LOST due to branch confusion. A "Root Cause" section at the bottom details that the fatal error was working in the wrong directory, resulting in the loss of the LockModel database model, 5 command handlers, and LockMiddleware. The interface features a sidebar on the left with various chat icons and a bottom input bar labeled "Nachricht" and "Menü".

Provided by @altbot, generated privately and locally using Qwen3.5:9b

🌱 Energy used: 9.123 Wh

@yacha

and at the end it lost all the work.

Working as intended: https://kind.social/@fadedoasis/116138767340284362

@Foxarc yes, they have absolutely no common sense, deleting the whole inbox or trying to fix the MR by pushing to an unrelated branch and spamming the MR page with "The task is 100% complete, it is safe to merge it now".

@yacha

"The task is 100% complete, it is safe to delete it now"

ftfy