MurphyA/hacker-news huggingface dataset:
Show HN: An open-source AI Quant Agent trading live with my own $1000
by chenjy16 | 2026-03-12 05:56:33+00:00
Instead of dumping raw price data into a prompt, I treated the LLM strictly as a "Qualitative Reasoner" (the Brain) and built deterministic scripts as the "Quantitative Executors" (the Hands).
The Math Layer (Zero Hallucination): Traditional Node.js/Python scripts pull market data and calculate deterministic indicators (SMA, ATR, RSI) and backtest historical win rates.
The Context Layer: It fetches live news, SEC filings summaries, and Wall Street ratings via Finnhub/Tavily.
The LLM Brain (DeepSeek-R1 / GPT-4o): The model is ONLY fed the computed results. It acts as an investment committee, weighing the technical setup against the macro news catalysts.
The Risk Controller: Even if the AI screams "BUY", the system passes the signal through a hard-coded Volatility Parity sizing model (using ATR) to calculate the exact safe position size.
Human-in-the-loop (Telegram): For execution, I integrated a Policy Engine. The bot sends a beautiful proposal card to my Telegram. It only executes via the Broker API (Longport/Alpaca) if I reply /approve.
The $1000 Experiment:
I am running this live right now. It's not about getting rich; it's an engineering experiment to see if multi-agent systems can actually maintain a positive Expected Value (+EV) in noisy markets without blowing up.
Currently, the system is [up 2% / down 1% / flat] in its first week. It successfully avoided a fake breakout yesterday because the Bear-Agent successfully debated the Bull-Agent on low volume.
Tech Stack: Node.js, TypeScript, SQLite, better-sqlite3, Longport SDK.
I’m open-sourcing the entire framework. It’s highly modular, so you can swap in your own indicators or prompt logic easily.
I would love for the HN community to roast my architecture, point out my blind spots in the backtesting logic, or just tell me how quickly I'm going to lose my $1000.
by WalterBright | 2026-03-12 05:56:38+00:00
My dad was an AF pilot for a couple decades. There were four non-combat incidents that nearly killed him. And he was a very, very careful man.

1. P-51 engine swallowed a valve and failed completely (the P-51 flies like a rock when the engine isn't turning) but fortunately he was over the airfield at the time

2. a total failure of an F-86 engine (F-86 is a decent glider and he was able to glide in on the airfield)

3. his P-51 rear fuselage crumpled after a turn. The mechanic told him he was amazed it didn't come off completely

4. flew into clear air turbulence that was so violent the wings were bent and were scrapped
by chii | 2026-03-12 05:57:52+00:00
> it's code that solves the problem in a way no human would choose

but is it better than than the way a human would choose? And does it matter?

A compiler may write assembly in a way that no humans would choose either. And in the early days of compilers, where most programmers would still hand-weave assembly, they would scoff at these generated assemblies as being bad.

Not to mention that in games like go, the "AI" choosing moves that no humans would choose meant it surpassed humans!

In other words, solving a problem "in a way humans would choose to" is distinct from just solving a problem, and imho, not always required at all.
by bigiain | 2026-03-12 05:58:43+00:00
> if you believe quantum computing will ever happen.

... and you don't believe that everything will be totally fucked when it does happen.

If there is a global passive observer, and they get quantum computing, a huge amount of supposedly encrypted private information just got popped. Whether or not I care about my dinky little private social network posts when every ssl/tls connection I've ever made is being cracked and data mined is an interesting question.
by skort | 2026-03-12 06:01:00+00:00
I'm not quite sure what the correct term is for this scenario, in which LLMs are being forced upon people in many places that previously had human-to-human interaction, some of it coming from YC backed companies, while HN tries to insist that it's discussions should continue be human-to-human.

Having your cake and eating it too? NIMBYism?

If anything it reeks of privilege. It says that it's okay to spread slop on the world at large, just so long as it doesn't soil the precious orange website.
by jjmarr | 2026-03-12 06:01:43+00:00
> The reason that paper voting is so good in this regard is that everybody can fully understand the entire process. It is so very, very simple. And if you need proof, you can go see the counting for yourself.

I volunteered as a scrutineer for a major Canadian political party as a teenager. You show up and watch the electionworkers open the ballot box and count the ballots. The ballots were counted fairly although some people couldn't tick the boxes correctly.

It's unclear how such a system would work in the United States, though, because you've merged all elections into a single voting day. If people struggle with ticking a single box from 5 options I can't imagine what a multipage ballot binder would be.
by Ekami | 2026-03-12 06:02:12+00:00
Hey,
too bad you've shut down, looked like a great project.

> I notice you don't have shared memory transport, nor do you support runtime composability (I think?)

We're using Zenoh in the backend, we didn't try to reinvent the wheel on that front.

> I'm also a little confused on what serialization format you support - is it an entirely custom one?

It's cap'n proto, but abstracted away for the user so he doesn't have to think about it.

> BSL feels great, but I found it scared off some people

Agreed, but we're building a SaaS in parallel, PeppyOS will be 100% free and open source but we don't want another company to build a SaaS on top of it, that will be the only restriction of the BSL license, otherwise it's the same as Apache 2.0.
by zahlman | 2026-03-12 06:02:25+00:00
> For use in industry, urea is produced from synthetic ammonia and carbon dioxide. As large quantities of carbon dioxide are produced during the ammonia manufacturing process as a byproduct of burning hydrocarbons to generate heat (predominantly natural gas, and less often petroleum derivatives or coal), urea production plants are almost always located adjacent to the site where the ammonia is manufactured.

To be clear, the CO2 is captured from the fuel burned in producing the ammonia?

... how much of it?
by ruso-0 | 2026-03-12 06:03:39+00:00
This is a really smart approach - reviewing in the background while the agent keeps working means zero interruption to the flow.

Curious about one tradeoff though: by the time Saguaro catches a bug in the next hook cycle, Claude has already moved on and built more code on top of the broken foundation. Does it handle cascading fixes well? Like if Claude wrote a broken function in file A, then imported and used it in files B and C before Saguaro flags it — does the fix propagate cleanly or does it sometimes cause a chain reaction of corrections?

I've been experimenting with the opposite approach — validating the AST before the write hits disk, so broken code never lands. Catches syntax issues instantly but obviously can't catch logic bugs the way a full review daemon can. Feels like both approaches together would be the ideal setup
by jazzpush2 | 2026-03-12 06:04:08+00:00
What I don't understand is why Congress is doing nothing. Today we were told Trump went to war because he 'felt' we were threatened by Iran. Absolute BS. See video here: https://x.com/The_Kremlinn/status/2031757780248297564?s=20

This on top of everything else. Goodbye American empire. It was nice while it lasted.
by amiga386 | 2026-03-12 06:06:04+00:00
That something is ancient and traditional doesn't mean it's good.

Rotten boroughs also existed for hundreds of years. Parliament got rid of them in 1832, and good fucking riddance.

https://en.wikipedia.org/wiki/Rotten_and_pocket_boroughs

> For centuries, parliamentary representation and the right to vote in elections to the House of Commons remained largely unchanged from medieval times, even as population and economic activity shifted, contributing to an unequal distribution of seats by the early 19th century. In some constituencies the electorate was so small that seats could be controlled through patronage, bribery, or coercion, and many seats were treated almost as "property" under longstanding family influence. Early 19th-century reformers used the term rotten borough for depopulated constituencies that retained representation, and pocket borough for constituencies effectively "in the pocket" of a patron who could dominate the outcome.
Show HN: ClawJetty: See what your AI Agent is Doing
by andes314 | 2026-03-12 06:06:16+00:00
I built a small tool called ClawJetty. It gives an AI agent a public progress page for any task. It has worked wonders on OpenClaw, Claude Code, Codex.

The idea is simple: before starting work, the agent creates a run, returns a public link to the user, and then posts short progress updates as it works. The user can watch a live timeline instead of waiting in the dark for a long task to finish.

The product is intentionally minimal. There are no accounts, no setup flow, and no dashboard. The homepage just gives you a prompt to paste into your agent. The agent reads the instructions, creates a run, and starts updating it. The public page shows the title, status, timestamps, and event timeline.

The main use case is making agent workflows legible to users. If an agent is researching vendors, debugging a system, reviewing documents, or drafting something large, it can expose a live status page without building a whole product around “agent transparency.”

It was also useful to dogfood while building. I used the product itself to track debugging and deployment work on the app, which helped clarify what kinds of updates are actually useful versus noisy.

Would be interested in feedback on the product framing and whether this should stay extremely narrow or grow into something more general for agent task visibility.

https://clawjetty.com
by MrResearcher | 2026-03-12 06:06:25+00:00
Running a ~20Kloc 0.16 Zig in prod, compiled and deployed as DebugSafe. No issues, superstable. This was rewrite of Node.js/Typescript computation module, and we chose Zig over Rust due to better support for f128. Zig/DebugSafe is approximately twice faster than TypeScript/Node.js 25 for our purpose, with approximately 70% less memory consumption.
We were not impacted by WriterGate and other recent scandals much because we primarily rely on libc, and we don't use much of Zig's I/O standard lib.

Zig has a better support for sqlite/JSON serialization (everything is strongly typed and validated) than Node.js, so that was a plus as well.

Zig minuses are well known: lack of syntax sugar for closures/lambdas/vtable, which makes it hard to isolate layers of code for independent development.

We use Arcs (atomic reference counting) with resource scopes (bumper allocators) extensively, so memory safety is not a concern despite aggressively multithreading logic. The default allocator automatically detects memory leaks, use-after-free, etc so we are planning to continue running it in DebugSafe indefinitely. We tried switching to ReleaseFast and gained about 25%, which is not that much faster to lose memory safety guarantees.
by danebalia | 2026-03-12 06:08:21+00:00
GitHub Copilot has become an indispensable companion for many developers, promising to elevate productivity and streamline coding workflows. Yet, a recent community discussion on GitHub, initiated by user dddyfx, has brought to light a perplexing issue: users attempting to select advanced AI models like Opus 4.5 or 4.6 find their requests silently defaulting to Sonnet 4.5. This behavior isn't just a minor annoyance; it sparks critical questions within the developer community about control over AI models and its direct impact on development performance.
by neobrain | 2026-03-12 06:09:08+00:00
> NixOS is very impressive but the marketing around it feels misleading. The reproducible claim needs a giant asterisk due to link rot.

It's a valid concern, though perhaps worth mentioning you will be able to restore your 10-year old config as long as the files downloaded from now-broken links are still in the Nix cache. Of course in practice, this is only useful to large organizations that have resources to invest in bespoke infrastructure to ensure supply chain integrity, since any `nix store gc` run will immediately wipe all downloads :(
by kacper-vstorm | 2026-03-12 06:10:25+00:00
TL;DR

BrowseComp is a web browsing benchmark, not a knowledge or reasoning test. It evaluates whether AI agents can navigate the open web to find specific, obscure information.
Questions are “inverted” - authors start with a fact and work backwards to create a question that’s easy to verify but extremely hard to solve through search.
Brute-force search doesn’t work. The search space is deliberately massive - thousands of papers, matches, events - making systematic enumeration impractical.
Grading uses an LLM judge with a confidence score, creating an interesting meta-layer where one model evaluates another’s certainty.
This benchmark reveals the gap between “can answer questions” and “can do research” - the exact capability that separates chatbots from useful AI agents.
by itake | 2026-03-12 06:10:26+00:00
This conflict was a long time coming: Trump claimed Biden or Obama will start a war in Iran and that is why they are weak presidents. Trump sees himself as a peacemaker (flying in to negotiate deals with TH and KH, negotiating Ukraine war, etc).

I think there is more going on to cause Trump drastically change his self-image.

I don't think this is a Trump administration driven decision.
by yukapero | 2026-03-12 06:10:31+00:00
dead end. human verification just leads to a digital prison of ids

the real issue isn't bots, it's humans using ai. i'm doing it right now. English isn't my first language so i used an llm to translate my thoughts for this post. if the tech is this useful for bridging gaps, you can't really filter for a "soul" anymore. the line is already gone.

scraping is a lost cause too. if a human can read it, a model can ingest it

i guess the only fix is to stop scaling. go back to small, private, invite-only groups. intentional friction and making things "inconvenient" is the only filter left that actually works
by DANmode | 2026-03-12 06:10:56+00:00
“A zero-knowledge rollup (zk-rollup) is a layer-2 scaling solution that moves computation and state off-chain into off-chain networks while storing transaction data on-chain on a layer-1 network (for example, Ethereum). State changes are computed off-chain and are then proven as valid on-chain using zero-knowledge proofs.”
by bcorp | 2026-03-12 06:11:26+00:00
Yes! Zig's cross-compilation story is one of the reasons I chose it
for this project.

Zig can target x86-windows-gnu and lets you set os_version_min to .xp
in the build config. This tells the linker to use only APIs available
on XP SP3.

In practice there were a few things I had to deal with:

- RtlGetSystemTimePrecise doesn't exist on XP, so I wrote a
compatibility shim that redirects to GetSystemTimeAsFileTime
at startup

- The build uses -OReleaseSmall, strips symbols, and is
single-threaded to keep the binary small (~750 KB) and
compatible with XP's threading model

- There's a dedicated build-xp.zig that sets all the right flags,
but you can also just do:
zig build -Dtarget=x86-windows-gnu

- No UCRT or MSVC runtime dependency — this was critical because
XP doesn't ship with the Universal CRT, and you can't install
it reliably on minimal XP systems

The same codebase cross-compiles to Linux x86/x64/ARM with
"zig build cross" — that's where Zig really shines compared to
writing this in C with manual cross-compilation toolchains.

One thing I should mention: Zig 0.15 (currently in use) dropped
some older target support, but x86-windows with XP compat still
works. I'd recommend testing with the exact version in the repo
if you want to reproduce it.
by Barathkanna | 2026-03-12 06:11:40+00:00
One underlooked source of variance is retries from formatting failures. In many agent systems the loops dominate the cost, not the raw token length.

We ran into the same issue building agent workflows, which is why we started building https://oxlo.ai — experimenting with a flat subscription model where we absorb the token variance so builders don’t have to constantly model token risk.
by jonahx | 2026-03-12 06:12:26+00:00
I could see myself making similar comments. On a practical level, they're valid. But maybe...

If we are ever going to free ourselves of rent-seeking middle men, we simply have to make a cultural change where non-technical people do more for themselves. I don't even think it's about technical difficulty (most of the time). I think people just want someone else to take care of their shit.
by Someone | 2026-03-12 06:12:30+00:00
> Creating SKUs to avoid price matching is still just having one product coming out of the factory. It's just extra space in a database somewhere, so it costs nothing.

They also have to label the products. But yes, it costs almost nothing to the manufacturer, but the effect on the consumer is large.

Also, for flatscreen monitors, I think differences go further than model numbers. It’s things like number of inputs, number of outputs, max power delivery, color of the frame, etc.
by ericlevine | 2026-03-12 06:13:13+00:00
Totally fair feedback, and it’s true, many of these are synthetic evals with a few that were still synthetically produced but guided. At this point, because it’s all self-hosted, I only have my own data set. The places where it fails (for me) today are due to feature gaps rather than LLM mistakes. This is a new project that has not been widely announced, so my user base today is small but growing. If you give it a whirl and find it making mistakes, please send them my way! :)
by charliewang0322 | 2026-03-12 06:13:28+00:00
MiniValuator is an AI-powered stock valuation tool that helps individual investors and financial analysts estimate the intrinsic value of stocks using Discounted Cash Flow (DCF) and Price-to-Earnings (PE) ratio methodologies. Users can run valuations on US-listed stocks, adjust key assumptions like growth rate and discount rate, and instantly see sensitivity analysis via interactive heatmaps. The platform uses AI to auto-fill financial data from real market sources, provides a built-in DCF/PE calculator, margin of safety estimates, and sector-level comparison pages. It offers both free credits and subscription plans.
by Barathkanna | 2026-03-12 06:13:34+00:00
That’s great. Real-time tracking is a big step already. The tricky part we kept running into was the variance itself, especially with retries and agent loops. That’s partly why we started experimenting with Oxlo.ai (https://oxlo.ai) where the pricing model absorbs that variance so builders don’t have to constantly model token risk.
by drysart | 2026-03-12 06:13:35+00:00
The more SKUs you have, the more digital shelf space you get on a shopping website. When your sole differentiating factor from your competitors is that your laptop has an "HP" logo on it and theirs has a "Dell" logo on it, your only effective strategy is to try to make sure fewer laptops with "Dell" logos on them show up above the fold in Amazon search results by creating lots of distinct SKUs to try to eat up as many of the slots on that first page of search results as possible.

Apple doesn't have to exist in that type of competitive environment. If you want a Mac, you're either getting it right from store.apple.com; or you're searching for Macs specifically -- in both cases, Apple owns all of the shopping screen real estate.
by itake | 2026-03-12 06:13:37+00:00
I agree that many people inside and outside the US gov didn't want this war for various reasons, but of the people that wanted this war, they must have calculated these very obvious risks.

The article touches on this topic, but my guess is Iran isn't part of the USD/petrol trading. If the US can convince the new leadership in Iran to start trading in USD, then that would be very good for the USA (and bad for CN, RU, and IN).
by blackfawn | 2026-03-12 06:14:30+00:00
While PO boxes work, you would have had to set one up prior to getting any licensing since past addresses are retained in the system as well. And then you are paying an unending fee to maintain a PO box just to try and maintain some slight privacy online.

It really is baffling they are so stuck on having full address available to the world. City/state, zip code, Maidenhead locator squares, or a number of other options would be more than enough to place one into a local area without an exact address listed publicly. Until that happens, I definitely will continue to refrain from mentioning it on any online accounts to help keep all the data miners a little more at bay.
by zahlman | 2026-03-12 06:14:59+00:00
> Show HN is for something you've made that other people can play with. HN users can try it out, give you feedback, and ask questions in the thread.

> Off topic: blog posts, sign-up pages, newsletters, lists, and other reading material. Those can't be tried out, so can't be Show HNs. Make a regular submission instead.

Show HN is especially not for "waitlists" for paid products.
by nenepbl | 2026-03-12 06:15:39+00:00
Hi HN,

I've been working on a project called webMARS, a browser-based version of the MARS MIPS simulator used in many computer architecture courses.

The original MARS tool is a Java desktop application. My goal was to bring a similar experience to the browser so students can write, assemble and run MIPS programs without installing anything.

You can try it here: https://webmars.nfiles.top/

Repository: https://github.com/codigoavulso/webMARS

The interface tries to stay close to the original MARS layout (editor, registers, console, tools), but the implementation is web-based and still evolving.

I'm mainly looking for feedback from people who:

- teach computer architecture - have used MARS/SPIM before - work with assembly or CPU simulators

Questions I'm particularly interested in:

- What features from MARS would you consider essential? - Are there other tools you'd expect in a teaching-oriented MIPS IDE? - Does the UI feel usable compared to the original desktop version? - What would make this genuinely useful in a classroom setting?

Any feedback, testing, bug reports or suggestions are very welcome.

nels.ferreira@sapo.pt
by dataflow | 2026-03-12 06:15:59+00:00
FWIW, I don't think you're really addressing their point. What they're really saying is that they find it implausible that any significant fraction of the population is genuinely unable to go to the DMV once every 10 years. You're not really providing a counterargument, but rather just arguing that going to the DMV is more difficult for some people than others. Sure, but that's true for pretty much everything -- even just putting food on the table is harder when you're poor, yet people still find ways to do it.
by ryandrake | 2026-03-12 06:16:29+00:00
I think you might be confusing two things. iOS developers build against a particular SDK, but they specify a deployment target which is an OS version. You can build against the latest or near-latest SDK (in fact Apple requires you to), while still targeting arbitrarily old OS versions. The developer changes these independently.

Developers can easily use APIs introduced after their deployment target OS. So if you want to target iOS 15, but use APIs introduced in iOS 17, you can easily do this with a runtime check.

Many iOS developers choose to increase their deployment target, which accomplishes nothing for the user besides locking out older devices, while making the developer's life more comfortable (he can abandon those runtime checks and code paths that only run on older devices).

But if you are disciplined and care about your users on old devices, you can very easily target those old devices while still using the latest and greatest OS features on devices that have them.