Robelkidin
Robelkidin on Hacker News
lmao codex vs Claude going to be like bmw vs Mercedes type of rivalry for the next decade
Posted by
Robelkidin on Thursday May 21, 2026 @07:36PM
from the self-post dept.
Very suspicious with openai codex getting better, I wonder if codex teams use Claude opus to build codex. Anyone engineer from openai who can confirm…
Posted by
Robelkidin on Tuesday May 05, 2026 @12:03PM
from the show-hn dept.
https://qlaud.ai
Here once again A Token Usage Meter for 12+ AI Providers Anthropic, OpenAI, Google, Alibaba qween, Moonshot Kimi, MiniMax, ElevenLabs, Deepgram, Perplexity. Qlaud.ai provides token usage meter / AI billing layer. Also Qlaud.ai provides Managed AI stack managed chats/DB, smart routing MCP/Tools CUSTOM json drop tools,A router to 12+ providers with one url change instead of Anthropic or ANY...
openAI closed down Sora too? How are they spending that much on compute. Anthropic seems realistic.
what do think AI will be in 5 years. currently CODING is solved.
there is obviously productivity increase with AI but it might have a ceiling. AI leader bluffing spending trillions is a joke. cost of ai gets cheaper, compute spend getting higher is just confusing. the gap is really huge. it seems just selling hype
Posted by
Robelkidin on Tuesday April 21, 2026 @12:01AM
from the self-post dept.
It really does not make sense spending trillions on compute. Is this suppose to be a hype for marketing. The way I see it, the price of AI is going down and getting cheaper every quarter. What can we expect in next couple of years. Also why is openclaw.ai landing page down?
we have 1000+ apps, but only 117+ that are non-technical friendly with simple to connect are rolled out.
we currently support 1000+ app integration. we have rolled out 117+ apps that simple to connect. We are rolling out the rest since they are not non-technical friendly.
Posted by
Robelkidin on Monday April 13, 2026 @08:43AM
from the AlitaGPT.com dept.
I have been experimenting with openclaw for the past 3 months and I am Software Engineer and I had difficulties setting it up and managing it. I almost bought Mac Studio to run it, bought into the hype. I do believe it absolutely amazing product. I recently launched AlitaGPT.COM (Alita.com was already registered) to provide a managed openclaw with hundreds of custom application integration. I used GCP GKE -Autopilot which is dedicated node for every customer which is costly on average $30-45/customer + AI API COST. I have launched couple managed openclaw on AlitaGPT and tried OpenAI GPT 5.1, worst and annoying models, it keeps asking for confirmation 10 times before doing a simple task. MiniMAX and Claude models tend to be better AI models at doing agentic tasks.
If @SAM_ATMAN keeps at this rate, MiniMax and Claude will takeover for B2B and B2C market.
not promotional post, but I would love to hear insights of HN engineers on AlitaGPT.COM . I built it for non-technical users who have no idea what openclaw is and I have integrated hundred of app OAUTH2. adding more apps.
shout out to OpenClaw.ai [https://github.com/openclaw/openclaw] contributors. Amazing work ;)
Posted by
Robelkidin on Friday April 10, 2026 @06:32AM
from the show-hn dept.
I have not done SOC 2 audit yet. LogClaw is configure to run locally and you can deploy it in your org. so technically all your data you can own them. Your logs go thru many steps. First thru ranking, only the flagged logs go to LLM usually 1-30% of your logs, LLM is used to understand the root cause and in creating a rich context incident ticket. LLM is not used to flag your logs. Currently we support standardized logs OTEL. so we can determine using our algo 99% of incidents.
And YES LogClaw.ai is able to injest terabytes of logs a day.
Also developer configure the alerting conditions. LogClaw it automatically finds your incidents with out manual setting up alerting conditions on your log dashboard [splunk/datadog logs]
Analyzing logs is not a LLM Foundation model issue.
LogClaw algorithm is the moat here that flags logs first. Those only flagged usually less than 10% of the logs are analyzed by LLM. LLM is great at finding root cause if the logs are clear and detailed. So the LLM heavily depends on the quality of your logs. So if your logs are rich with info, it will have a better insights at understanding it.
I'm waiting for Anthropic's Email. I guess it is not as important as OpenClaw.
Appreciate it. try logclaw, we need your software insights on it.
I meant since this is designed to be deployed in companies private VPC, their data stays with them. Zero vendor data risk. Corrected it. Thanks for pointing it out.
Thanks for pointing out. Try logclaw and we need your input instead,
We have Algorithm in place. Our system is capable of injesting terabytes of logs first it goes thru an algorithm that ranks every logs. ti simple put this, majority of logs are successful request or health checks or similar are ranked low and not sent to llm. Only those flagged above certain threshold are then analyzed by retrieving all the logs associated with it and analyzed for second time with LLM if its worthy of a ticket.
Yes LogClaw does that. It has ranking algorithm if anomaly is worthy of a ticket it will give you metrics blast radius and evidence logs. all the logs related to that issue. Similar incidents are grouped into one ticket.
LogClaw capable of injesting terabytes of logs a day. Our algorithm simply ignores successful request lifecycles which can help reduce the strains in analyzing terabytes of logs. Our algorithm then ranks and flags potential logs. later on we retrieve all logs associated with that log and analyze it more based on metrics if its worthy of a ticket/incident.
ALL existing product simply let you set up alerting system, and that alerting system is manually done by you. still un-expected issue can arise. LogClaw is not altering system. you just send all your logs, its capable of injecting terabytes of logs per day, and it automatically ignores all the successful logs, and it works on the uncaught exceptions, errors from all services, infrastructure itself.
Exactly. Incidents happen with uncaught issue. A simple of database query slowness or out of memory ...etc can cause your "perfectly designed feature" to cause P1. So it is super convienet for a system that invests all of your logs and monitors it for you. No need to customary set up alerts or trace traceIDs, connect logs through out micro-services.