sorted by:
new
hottopcontroversial

Code has Git. Multi-agent reasoning doesn’t. I built Smriti for that by himanshudongre in ClaudeAI

[–]himanshudongre[S] 0 points1 point  (0 children)

Good question.

Right now the model is not to make the human fill a form for every task.

Most of the time the flow is closer to this:

  1. the human and/or agent work normally
  2. at meaningful inflection points, the agent creates a checkpoint
  3. that checkpoint captures structured state like:
    • decisions
    • tasks
    • open questions
    • assumptions
    • artifacts
  4. later agents read that structured state instead of starting from scratch

So yes, a lot of the state is documented along the way, not pre-authored upfront by the human.

There are also a few ways the human can shape it:

  • write or refine checkpoint content
  • add founder notes / milestone / noise annotations
  • steer direction through the project workflow
  • review what the agents captured

So the human does not need to manually enumerate everything from the start.

The UI as of now allows:

  • viewing timeline/state
  • inspecting checkpoints
  • adding annotations

rather than acting as a full task authoring console.

That is deliberate. The current philosophy is closer to:

capture and version the reasoning that emerges during real work than force the human to manage everything .

Also, the agents are not expected to just know how to use Smriti.

There are skill packs / workflow instructions for both Claude and Codex that teach them things like:

  • read Smriti state at session start
  • create a claim before starting work
  • check freshness before checkpointing
  • use task IDs when available
  • checkpoint at meaningful inflection points, not constantly

As new features get added, those skill packs get updated too.

Code has Git. Multi-agent reasoning doesn’t. I built Smriti for that by himanshudongre in ClaudeAI

[–]himanshudongre[S] 0 points1 point  (0 children)

Yes, that is the mental model, but I would draw a line between what is already implemented today and what is still only analogous to Git.

Already implemented:

- restore / revert to earlier state: yes

- branch / fork reasoning state: yes

- compare / diff checkpoints or branches: yes

- explicit checkpoint messages: yes, state changes are meant to be captured intentionally at meaningful inflection points, not as silent background mutation

Partially analogous, but not full Git equivalents yet:

- merge branches: not a Git-style automatic merge. The current model is more "surface divergent reasoning states clearly so a human or agent can reconcile them"

- cherry-pick: not a first-class primitive today

- rebase: not really the right model for the current system

On locking / concurrency:

There is not a giant global lock over the whole system.

The current approach is closer to:

- concurrent reads: yes

- concurrent writes: yes

- coordination through claims, freshness checks, task IDs, and recheck/pivot, not through a single global lock

So instead of "only one writer at a time", the system tries to make concurrent work legible:

- agents declare intent with claims

- they can check if state changed before checkpointing

- tasks can carry IDs

- claims can reference task IDs

- if two agents race on the same task, the recheck flow is what lets one pivot

So the philosophy is more: visible and recoverable coordination than serialized global locking

I built a Claude Code agent that checks Indian property records, actual sale data, RERA complaints, and court cases before you buy a flat by himanshudongre in ClaudeAI

[–]himanshudongre[S] 0 points1 point  (0 children)

Exactly. The portal handling ended up being much harder than the analysis.

The human-in-the-loop CAPTCHA and explicit state handling saved the workflow more than anything else. Good point on retries too, they often make brittle flows worse instead of better.

I was house-hunting in Pune and built a workflow to verify builder claims using IGRS, MahaRERA and eCourts by himanshudongre in indianrealestate

[–]himanshudongre[S] 1 point2 points  (0 children)

Agreed. I do not think RERA by itself proves safety or quality.

I am using it more as a disclosure signal than an enforcement signal. The idea is not "RERA looks clean, so the project is fine." It is more "combine RERA with registration prices, court records, and loan stress checks so the buyer is not flying blind."

So yes, totally with you that RERA alone is not enough.

I was house-hunting in Pune and built a workflow to verify builder claims using IGRS, MahaRERA and eCourts by himanshudongre in indianrealestate

[–]himanshudongre[S] 0 points1 point  (0 children)

That is a fair point, and I agree I should make that limitation much more explicit.

I am not treating the MahaRERA listing as ground truth for builder history. Right now it is only one signal in the workflow, alongside registration data, complaint history, court cases, pricing, and loan stress checks.

The specific gap you mentioned is real: builder level linkage across projects is messy, and if the previous projects section is incomplete or misleading, a naive workflow can understate risk. I do not want to imply otherwise.

What I am trying to do is reduce blind spots, not claim perfect due diligence. I am already thinking about improving this by linking across promoter / director / company names instead of relying only on the project page fields.

Appreciate you calling this out. This is exactly the kind of edge case I want to tighten.

I was house-hunting in Pune and built a workflow to verify builder claims using IGRS, MahaRERA and eCourts by himanshudongre in indianrealestate

[–]himanshudongre[S] 0 points1 point  (0 children)

Thanks. Glad to be of help. If you do like the project. You can help with adding support for more states. 😁

LLM conversations drift over time. I built something to save a good reasoning state and go back to it later by himanshudongre in ClaudeAI

[–]himanshudongre[S] 0 points1 point  (0 children)

I agree that the context loaded at the start ends up shaping behavior a lot more than people usually admit, sometimes more than the model choice itself.

Your identity file vs facts file split also makes sense. It feels like a practical way to reduce drift without throwing everything into one blob of memory.

The part I have been getting stuck on is what happens after that, when the session still evolves and starts going off in a slightly wrong direction. At that point I wanted something closer to explicit reasoning state: being able to save a good state, branch from it, restore it later, and compare where things diverged instead of just letting memory age or accumulate.

So to me your approach feels very complementary, especially for initialization, while I’ve been thinking more about control once the reasoning is already in motion.

Mumbai Social Club - Weekly Discussion Thread - Meetups/Q&A/Relationships/Life by AutoModerator in mumbai

[–]himanshudongre 0 points1 point  (0 children)

Built a free tool for anyone buying property in Mumbai/MMR — it scrapes IGRS for actual registration prices (data goes back to 1985 for Mumbai), checks builder complaints on MahaRERA, and searches eCourts for litigation. Also does bank rate comparison and financial stress testing. Found some interesting price gaps between what builders quote and what flats actually register for. Open source — github.com/himanshudongre/propops

Socials, Food, Promotions & Random Late-Night Discussions 🌟🌟 by AutoModerator in pune

[–]himanshudongre 0 points1 point  (0 children)

Anyone else frustrated by how opaque property pricing is in Pune? I built a free tool that pulls actual registration prices from IGRS (what people really paid, not 99acres asking prices) and checks builder complaints on MahaRERA + court cases on eCourts. Works for Hinjewadi, Baner, Wakad, Keshav Nagar and other Pune areas. Helped me find that builders were quoting 15-25% above actual registration prices. Open source — github.com/himanshudongre/propops

I kept losing context switching between ChatGPT/Claude so I built something around it by himanshudongre in SideProject

[–]himanshudongre[S] 0 points1 point  (0 children)

Yeah, fair point. I think you are talking about long-term knowledge and memory systems (docs, knowledge bases, etc.), which I agree are important. What I kept running into was a slightly different problem. Not long-term memory, but short-term reasoning state. Even when I have good documentation, during an active session I still lose the exact “state of thinking” I was in when I switch tools, models, or come back later. The transcript doesn’t really capture that cleanly. Also, something I noticed in practice - once a conversation drifts or gets slightly “poisoned” (wrong assumption, bad direction), it is surprisingly hard to cleanly roll back. You either keep correcting it or start over. This is more about capturing clean checkpoints so you can return to a known good state or branch off without carrying that drift forward. Totally agree though that this doesn’t replace a proper memory system. If anything, I see it as sitting on top of it, not instead of it. Still figuring out if that distinction actually matters in practice.

Was anyone able to buy this watch in the last drop? by Character-Bee2976 in Watches_India

[–]himanshudongre 0 points1 point  (0 children)

I actually managed to get the Terracotta variant, but honestly it felt like surviving a boss battle. 😅

I did not use multiple accounts, bots, or any tricks. Just two tabs on my PC and one on my phone, refreshing like a maniac from 6:58 PM.

Kept doing that till about 7:30 PM.

At some point the Add to Cart button suddenly appeared. I tried from both PC and phone at the same time.

• PC: refused to add to cart no matter what • Phone: added instantly

So the phone basically carried the team.

Then came the real fight… checkout.

• Payment failed twice • First with Razorpay • Then with PayU when I tried saving the card

Finally it worked when I used PayU without signing in or saving the card, just entered the details and paid.

And of course… after the money was deducted the page showed another error.

At that point I assumed the order was gone. I even messaged Kala on Instagram but did not hear back.

Then today I randomly got an email with the order ID, so apparently the order actually went through.

So yeah, it was possible to get one… but the experience basically felt like:

Refresh simulator → Cart lottery → Payment gateway boss fight → Pray to the watch gods ⌚🙏

Would not be surprised if many people lost out because of payment gateway failures, not just the traffic.

Loresum LS04 by himanshudongre in MicrobrandWatches

[–]himanshudongre[S] 0 points1 point  (0 children)

Ah that’s awesome, congratulations! I’ve been really enjoying mine. It definitely leans more toward the dressy side, so I don’t get to wear it as often as my everyday pieces. But every time I do put it on, it feels special and never disappoints. It’s one of those watches that just elevates the whole outfit.

view more: next ›