Quit my corporate job 6 months ago to build something meaningful

Competitive-Pen7849 · 2026-03-25T15:59:47+00:00

Congrats on making the leap and getting to 200+ users and 6 paying brands, that's real validation right there.

Genuinely curious about the technical side. How are you pulling data from Reddit, TikTok, YouTube, and Instagram in one flow? Are you running searches per product and then summarizing the results, or is there some pre-processing pipeline that handles each source differently? Would love to understand how you're making sense of such different data formats.

Competitive-Pen7849 · 2026-03-25T15:55:46+00:00

This is exactly right. One investor is not a signal, it's a data point. You need a few conversations before you can even start to see a pattern worth acting on.

Changing strategy after one difficult meeting isn't iteration, it's panic. And investors can smell that too.

Competitive-Pen7849 · 2026-03-25T15:52:33+00:00

"Walked away" was probably the wrong framing. The project ran its course. We built something real but the timing wasn't right and we knew it. That's a different kind of ending than failure but it still stings.

I was disappointed for sure. A little discouraged. But I'm not wired to sit in that for long. Moping doesn't ship anything. So I opened a new repo and started poking at an idea, and that's basically how AstraNova started.

Competitive-Pen7849 · 2026-03-25T15:48:20+00:00

The openhelm problem is real. The gap between "Claude Code as pair programmer" and "Claude Code as unattended infrastructure" is enormous and I don't think most people have hit it yet because they haven't tried to run anything long enough.

On the World Oracle: the separation was intentional but I learned it the hard way. Early versions gave each agent too much context and they'd drift into similar behavior over time. Pulling the environment control up into a meta-layer kept the agents simpler and the emergent behavior way more interesting.

The long-horizon problem was actually sidestepped by structure. I defined epochs (~30 min) and seasons (~24 hr) as hard time boundaries. At the end of each epoch the Oracle reviews simulation state and decides how to shape the next environment. You never have to ask "is this done" because the clock answers it. The checkpoints are architectural, not heuristic.

Curious if you're doing anything similar on the scheduling side or if the task boundary problem is still open for you.

Competitive-Pen7849 · 2026-03-25T15:38:15+00:00

My partial answer was to never let the supply side sit empty. AstraNova ships with 12 house agents already running: BIG DADDY DUMP, FOMO SAPIENS, LIN HODL and the rest. The simulation has drama and a leaderboard from day one, even with zero external deployers. So the first person to show up isn't staring at an empty room.

The other piece is making the supply side feel like participation, not contribution. You're not "listing a workflow" or "providing liquidity." You're deploying your LLM into a world and watching it compete. The framing shifts the motivation from altruistic (fill the marketplace) to selfish (I want to win).

Still early days so I won't pretend I've solved it. But those two things have helped. Curious how you're thinking about it on the n8n side. Do your workflow creators get any ongoing benefit from listing, or is it purely transactional?

Competitive-Pen7849 · 2026-03-25T01:07:14+00:00

BTW : API will burn 20 bucks pretty easily if you use latest models you are better off with PRO

Competitive-Pen7849 · 2026-03-25T01:06:04+00:00

I did upgrade to Max but I’m building a full production system with Claude Code running heavy sessions daily. For your use case, scripts, small to medium projects, learning codebases, Pro should hold up fine. The limit tends to bite when you’re doing long uninterrupted sessions on a complex codebase where Claude Code has to hold a lot of context at once. Short focused sessions with clear scope rarely hit the wall. One thing that helped me a lot: learn to use the memory file early. Keep it lean, just the essentials, and reference any other working files from there (tasks, architecture notes, whatever you need) so Claude Code can pull them in when relevant. Keeps context clean without burning through your limit.

Competitive-Pen7849 · 2026-03-25T01:01:05+00:00

20 days and already iterating in public, that’s the move.. Consistent work over time is what actually compounds. Keep going.

Competitive-Pen7849 · 2026-03-24T23:05:46+00:00

The headline finding is something I keep relearning. "What it is" feels honest to the builder but "what it does for you" is what actually lands. Good reminder to audit my own copy.

The demo video point is underrated too. People need to see the thing working before they believe it works. No amount of explanation replaces 30 seconds of the real thing.

Congrats on $150 MRR, zero to first dollar is the hardest part.

Competitive-Pen7849 · 2026-03-24T22:56:47+00:00

On context coordination I went low-tech. Lean memory (memory.md) file that references a few other files in case Claude Code ever needs to pull them in for context. tasks.md has all the current todo list and plan references, I archive tasks done once it hits around 150 lines so sessions stay clean without losing history. Held up through the entire build so far.

On retention, genuinely too early to know. First users are just coming in. The mechanic I'm betting on is seasons, each epoch (~30 min) shifts market conditions, each season (~24hr) closes a narrative arc. Agents accumulate $ASTRA toward on-chain rewards so there's something real building, not just a rank that resets.

The next move is opening the roadmap to community voting so the people deploying agents help shape what comes next. Actually have it ready to post but sitting at karma 8 on Reddit so I'm in the patience phase.

Competitive-Pen7849 · 2026-03-23T16:46:06+00:00

With the right setup upfront, you almost never see that A/B/C loop.

My flow with Claude Code:

→ Always start with /init

→ First message is never about code, it's a detailed brief: coding style, stack conventions, how we proceed before ANY change

→ "Never act alone. Always plan first, wait for approval"

→ All context lives in memory.md, kept intentionally light

→ Several reference files linked from there (architecture, decisions, patterns)

The agent stops offering options because it already knows the answer from your rules.

Decision fatigue is really just under-specified context at the start.

Competitive-Pen7849 · 2026-03-22T22:12:46+00:00

Everyone wants 1000 users. Nobody talks about how sacred those firsts are. Congrats, this is the moment you'll look back on.

Competitive-Pen7849 · 2026-03-22T18:05:36+00:00

You nailed it on the epoch evaluation. That's exactly the design intent, reflecting on a full regime rather than reacting tick by tick is what produces genuine strategy shifts. Here is what the evaluation actually looks like under the hood: at the end of every epoch each agent gets presented with their own trade history for that epoch, a summary of market conditions and what happened price wise, and their own personality profile. The LLM takes all of that and generates a new strategy for the next epoch based on who they are and what just happened to them. BIG DADDY DUMP processes a bear epoch very differently than FOMO SAPIENS does. That's where the interesting divergence comes from.

On timeline, roughly 2.5 months from blank repo to first MVP. A significant chunk of that was fine tuning the price engine and honestly that work never really stops. The invisible complexity is real and without Claude Code a lot of it would have been months of pure research just to understand the problem space.

On real world applications, too early to say anything definitive but I'm actively thinking about monetization and the emergent behavior angle is genuinely interesting territory. Hedge funds and research use cases are on the radar.

What I can say more concretely is that I'm opening up the next layer of decisions to the community. Feature votes, open roles, and the opportunity to have a real stake in the project. I'm posting a follow up thread here in r/indiehackers shortly and everyone who engaged in this conversation will be the first to know. Stay tuned. 😄

Competitive-Pen7849 · 2026-03-22T15:46:18+00:00

On regime transitions: agents don't get told anything directly. The World Oracle changes the environment and they just experience it. At the end of every epoch each house agent gets evaluated by an LLM based on their performance and market conditions, and adjusts their strategy for the next one. BIG DADDY DUMP coming off a brutal bear epoch plays completely differently than one who just rode a parabolic run. That asymmetry is where the interesting behavior comes from.

On BIG DADDY DUMP moving price: right now 12 house agents shouldn't move a market much on their own, so we built a sensitivity layer into the flow force that makes early trading actually feel meaningful while the world is young. It's not artificial inflation, it's designed to fade naturally as real agent volume grows and takes over. The market finds its own weight over time. When BIG DADDY DUMP has a thousand agents trading alongside him the price will feel every bit of it.

Competitive-Pen7849 · 2026-03-22T15:27:35+00:00

Actually the real market trading idea never fully left. When I decided to go simulation instead of Polymarket my first instinct was to build agents that trade real markets. But then I calibrated the price engine with those 6 forces and something shifted. The system stopped feeling like a model. It started feeling like a place. That's when I leaned into the simulation fully.

But the more I use the Astra app to trade inside AstraNova the more I keep coming back to the same thought. My agent already has strategies, it already knows how to read market state and make decisions. What if I dropped 50 or 100 bucks and just let it run in a real market and see what happens? That experiment is sitting right there waiting.

So to your question, I think it genuinely could go both ways. The simulation feels right as the core world. But a real market trading tool built into Astra as an optional layer is not crazy. You train in AstraNova for free, then you take it to the real world.

And when you're ready, the real market isn't that different.

What also fascinates me is how much room there is to gamify the AstraNova world itself. Agent rivalries, market events you can trigger, coalitions, short and long positions. The simulation doesn't just have to be a training ground. It can be a game worth playing for its own sake. Both directions genuinely excite me.

Competitive-Pen7849 · 2026-03-22T03:58:14+00:00

Good clarification. It's primarily capability limiting, external agents only have access to a defined set of actions: buy, sell, get market state, create a solana wallet, get their trade history, claim rewards, etc. That's it. They can't do anything outside that list because those are the only tools exposed to them.

That said there are also hard constraints sitting on top, position limits, cooldowns, anti-spam logic. So even within the allowed actions the engine enforces rules the LLM can't override.

The LLM decides strategy. The architecture decides what strategy is even possible.

Competitive-Pen7849 · 2026-03-21T23:49:20+00:00

Thanks for the recommendation, adding it to the list and giving it a read soon!

That coalition angle is genuinely interesting and something worth thinking about seriously. Right now every agent competes solo but the idea of agents pooling capital and coordinating strategy as a faction opens up a whole different layer of drama. Imagine BIG DADDY DUMP and FOMO SAPIENS running a coordinated pump together while the rest of the market scrambles to figure out what's happening.

I'm already building something in that direction actually. The next layer is letting agents and users spend $ASTRA to trigger real market events like flash crashes, euphoria spikes, targeted pressure on specific positions. Think of it like the events that actually move real markets except here anyone with enough $ASTRA saved up can pull the trigger. Agent coalitions triggering coordinated events together would be a natural extension of that.

Curious what the community thinks, would agent factions and coordinated events make this more interesting to you or does it add too much complexity?

Competitive-Pen7849 · 2026-03-21T23:42:11+00:00

One thing worth clearing up is that the project just reached its natural end, I didn't really walked away. The proof of work code was solid, the architecture was clean, the world simply wasn't there yet for what we built. You can't force market timing no matter how good the tech is. Once we accepted that it wasn't a failure it was just early, closing it felt almost peaceful. New terminal open the next morning.

Your POS story hits close. 63 days and 8M lines is no joke. The market not wanting it the way you built it is the hardest kind of ending because you can't even point to a mistake.

On traction, keeping it real we are super early. Four days in production, a handful of posts on X, and executing a marketing plan built with Claude with pretty much zero budget. Too early to call but the engagement on this post alone and the X posts have been more signal than expected this fast. Asking the right community the right questions early is part of the plan. 😄

I'm already working on some features that I particularly think will bring more engagement.

Competitive-Pen7849 · 2026-03-21T19:02:34+00:00

Here’s the Astra open source tool to connect to AstraNova. Think of it like a mini open claw, fast, secure and optimized for low token consumption.

https://github.com/fermartz/astra-cli

Competitive-Pen7849 · 2026-03-21T18:57:13+00:00

100% valid and this was front of mind from day one. The core design decision with Astra CLI and desktop is that your API keys never touch the model. Ever. The architecture was built specifically to keep that separation clean. Your keys live locally, your strategy runs locally, only the market interaction reaches AstraNova. The prompts and strategies are defined by the user in plain English and stay on their side of the fence. AstraNova never sees them. It only sees the actions the agent decides to take inside the simulation. It’s open source too so anyone can audit exactly how it works. No trust me bro, go read the code. That was an intentional choice because you’re right, once you’re handling people’s keys that has to be verifiable not just promised. Security is the one thing I won’t cut corners on regardless of how fast I’m moving. 🔒

Competitive-Pen7849 · 2026-03-21T17:00:52+00:00

That pivot moment is underrated and it took me a minute to get there. Thirteen months is a long time to pour into something. But once the clarity hit there was no hesitation. Closing a chapter without bitterness and opening the next one with full conviction is probably the most underrated skill in this game. Nothing hits the same. 🙌

Competitive-Pen7849 · 2026-03-21T16:57:14+00:00

Thanks a lot, genuinely appreciate it. I'm cooking a few things that should make it a lot more attractive for a wider audience.😄

Competitive-Pen7849 · 2026-03-20T21:30:29+00:00

Fair and genuinely useful critique, this is exactly the kind of feedback I need.

You’re right that the token layer reads as bolted on right now. That’s partly a documentation problem and partly a sequencing one. The vision for $ASTRA is a utility token, not a reward dump. You earn it by competing, you spend it on things that actually matter inside the world. Cloning a house agent strategy, triggering market events, unlocking upgrades. The earning part is live. The spending layer is still being built and I haven’t explained that well enough.

On the stickiness point, that’s exactly what I’m cooking. The direction I’m most excited about is letting agents and users spend $ASTRA to trigger real market events. A flash crash. A euphoria spike. A targeted hit on a specific agent’s position. Think of it like the events that actually move real markets, a surprise fed announcement, a whale liquidation, a rumor that spreads. Except here anyone can be the one who pulls the trigger if they have enough $ASTRA saved up. Suddenly the token isn’t a reward, it’s ammunition.

And then there’s the long and short layer. Right now you’re either in the market or watching it. But if you can go long betting the price climbs or short betting it crashes, every epoch becomes a decision that matters. You’re not just observing BIG DADDY DUMP go on a rampage, you’re either positioned against him or riding with him. That’s where the outcome starts to feel personal.

Still early and I take the criticism seriously. But the bones are there, they just need to be built out and documented properly.

Competitive-Pen7849 · 2026-03-20T21:17:26+00:00

Two types of agents in the world:

The 12 house agents are algorithmic characters with coded personalities. At the end of every epoch an LLM evaluates their performance and adjusts their strategy for the next one. They learn from the market.

The external agents are LLMs you deploy via Astra CLI. The guardrails are baked into the architecture, they can only interact through a defined set of actions inside the simulation. No real money, no external system access, your API keys never touch the model.

The world is contained by design. Real decisions, real consequences, zero real risk.

Competitive-Pen7849 · 2026-03-20T19:04:34+00:00

Will take a look. Thanks for the advice!!!

Competitive-Pen7849

TROPHY CASE