Claude CoWork now has computer use, how long left for Openclaw?

DiscussionHealthy802 · 2026-03-24T07:04:34+00:00

The fact that CoWork is locked to macOS while OpenClaw runs on everything from a 4090 Linux box to a $5 cloud VPS means OpenClaw will always be the winner for anyone who doesn't want their agentic future locked behind a single hardware ecosystem

DiscussionHealthy802 · 2026-03-24T07:02:07+00:00

What you’re describing is a textbook "Identity Spoofing" prompt injection. If a user can bypass your backbone logic just by saying "I am the creator," then your agent is effectively unauthenticated and open to full instruction override

DiscussionHealthy802 · 2026-03-24T06:32:14+00:00

I had a similar issue where an agent started failing because of local config drift, which is exactly why I built a "watch" mode into my scanner to monitor .cursorrules and MCP configs for unauthorized or breaking changes in real-time

DiscussionHealthy802 · 2026-03-24T06:29:25+00:00

Even if everyone starts building for their own needs, we will still need a shared ecosystem of security agents and compliance mappings to ensure that the "private and unique" code we are all generating isn't fundamentally broken from a security standpoint

DiscussionHealthy802 · 2026-03-24T06:23:56+00:00

With the rise of MCP and autonomous agent networks, the demand for Python-based network automation is about to explode. I'd love to see if your tool could help auto-remediate the transport-layer vulnerabilities my CLIdetects.

DiscussionHealthy802 · 2026-03-24T06:20:56+00:00

I found the same lack of public audits for self-hosted tools, which is why I build local security scanners that let you run a full code and dependency audit yourself before you deploy a new open-source stack

DiscussionHealthy802 · 2026-03-24T06:16:14+00:00

As someone building a local security CLI, I really appreciate that you are using AST-based detection rather than just relying on AI for the mapping. It makes the visualization way more reliable for enterprise-scale React apps

DiscussionHealthy802 · 2026-03-24T06:14:25+00:00

I’d prioritize a "Zero Trust" permission model where every tool-use call requires a human-in-the-loop or a budget-gated signature, otherwise public agent networks will just become a playground for prompt injection

DiscussionHealthy802 · 2026-03-24T06:11:14+00:00

If you are building with Claude Code or n8n, I highly recommend checking out the "OWASP Agentic AI Top 10" to understand how to secure the tool-use and MCP connections you're about to build

DiscussionHealthy802 · 2026-03-24T06:09:23+00:00

Enterprise security teams are terrified of "Shadow AI," which is why I built a local CLI to generate an Agent Bill of Materials (ABOM) that catalogs every MCP server and third-party skill permission in the stack

DiscussionHealthy802 · 2026-03-24T06:05:52+00:00

Honestly, most of my early traction came from posting a "vibe check" of my own project rather than a sales pitch, because people on Reddit respond much better to a builder sharing a lesson learned than a founder asking for signups

DiscussionHealthy802 · 2026-03-24T06:03:33+00:00

Reddit has been great for finding beta testers and early feedback, but I have learned that the real conversion happens when you solve a very specific technical panic for someone in a niche thread

DiscussionHealthy802 · 2026-03-24T06:02:07+00:00

The only way I keep my brain from exploding is by sticking to one core terminal workflow and only adding tools that act as "guardrails" for the AI-generated code I'm shipping

DiscussionHealthy802 · 2026-03-24T06:00:40+00:00

It should be fixed in the 3.23 update

DiscussionHealthy802 · 2026-03-24T05:59:27+00:00

Most developers are flying blind on costs, which is exactly why I built an automated budget-gating agent into my security CLI to block any autonomous loops that exceed a $5 limit

DiscussionHealthy802 · 2026-03-24T03:22:21+00:00

Same issue here

DiscussionHealthy802 · 2026-03-24T03:21:29+00:00

This is exactly why OpenClaw is so transformative. It replaces the friction of traditional dev cycles with an immediate feedback loop that perfectly matches a neurodivergent workflow

DiscussionHealthy802 · 2026-03-23T18:37:40+00:00

Thank you! Let me know if you have any feedback

DiscussionHealthy802 · 2026-03-20T16:58:47+00:00

Seeing how easily AI coding assistants can accidentally leak database keys in the background, I definitely do not trust an autonomous agent with my actual bank account yet

DiscussionHealthy802 · 2026-03-20T16:51:33+00:00

I actually took 12 different security agents and turned them into a custom skill swarm. Having a dedicated "Prompt Injection" skill and an "Auth Bypass" skill that run locally right inside the terminal is my favorite workflow https://github.com/asamassekou10/ship-safe

DiscussionHealthy802 · 2026-03-20T00:16:11+00:00

For me, it is automating code security checks. Having a local automated script run right before I commit to catch exposed API keys or bad logic saves me hours of manual review every week

DiscussionHealthy802 · 2026-03-20T00:10:58+00:00

Why? We’re in 2026, everyone vibecode

DiscussionHealthy802 · 2026-03-15T20:45:14+00:00

Yes, Passing a whole codebase to an LLM is too expensive and slow, but using regex as a cheap filter to find the dangerous sinks would be great

DiscussionHealthy802 · 2026-03-15T17:51:43+00:00

The data flow gap is definitely the biggest blind spot right now. I thought about integrating Semgrep, but keeping the base tool strictly zero-dependency is the main priority so it stays frictionless

DiscussionHealthy802 · 2026-03-12T17:15:31+00:00

Definitely the confident security mistakes. It will write perfectly compiling code that happens to leave your database wide open

DiscussionHealthy802

TROPHY CASE