Login

u/Existing_Tea_3064

r/AgentsOfAI r/ControlProblem r/SideProject r/claude r/AIMain r/iitbombay r/Agent_AI r/WhatIsMyCQS
▲ 0 r/AIMain

Majority people are using AI wrong and judging future based on it

We are now in a position where a tiny proportion of the population uses Fable or Opus or soon GPT-5.6 Sol, while everyone else's experience of Al is smaller models - Google's Al Overviews, Meta Al, ChatGPT free tier, maybe MS Copilot at max. People outside of tech must be completely baffled how this is supposed to take their damn job, and annoyed that hundreds of billions are being poured into it. But we all know...

reddit.com
u/Existing_Tea_3064 — 2 days ago
▲ 104 r/claude

Fable isn't fable anymore

For every damn small query, even when not related to bio/army/security, it keeps delegating to opus 4-8. And why the fcuk I can't use it for even planning out the code. That too keeps falling back to opus 😭😭

Take more money but bring back the old fable

reddit.com
u/Existing_Tea_3064 — 4 days ago
▲ 73 r/Agent_AI+3 crossposts

Who's watching the AI agents?

That question from Satya Nadella in the attached clip immediately caught my attention.

Not because it gave me the idea.

Because during my last semester, I was already running into the same problem while experimenting with AI agents.

The first demos were exciting.

But the first time an agent could call APIs, update records, send emails, or trigger workflows, the conversation changed completely.

It wasn't about model intelligence anymore.

It was about trust.

What is this agent actually allowed to do?

Who approved this action?

If something changes tomorrow, does yesterday's approval still hold?

Six months later, can anyone explain why an agent was allowed to perform a particular action?

I assumed there was already a standard way to solve this.

There wasn't.

So instead of guessing, I started talking to people.

Over the last month, I spoke with 30+ engineers, developers, and founders building AI products.

Despite working on completely different products, almost everyone described the same problems.

The approval lacked context.

The audit trail was an afterthought.

Permissions drifted.

State changed before execution.

Every team was quietly building its own control layer around AI agents.

That realization is what led me to build Duct.

Duct sits between your product and its callers—human or AI. A single manifest defines what actions exist, which are agent-accessible, which require approval, and every action executes with scoped permissions, explicit versioning, and a complete audit trail.

Every company can build this themselves.

Just like every company can build authentication or integrate directly with payment processors.

Yet most products choose Sign in with Google, Auth0, or Stripe—not because building v1 is impossible, but because maintaining identity, security, compliance, edge cases, and reliability eventually becomes a product of its own.

I believe AI governance is heading down the same path.

The question isn't whether engineering teams can build an AI control layer.

It's whether, five years from now, they'll still want to.

u/Existing_Tea_3064 — 4 days ago
▲ 5 r/iitbombay

Reducing placement/intern guesswork - looking for a club to take this forward

During placement and intern season, we'd spend hours trying to figure out things that should just be known: Did this company open last year? What was the CPI cutoff? What did they pay? Did they actually come or ghost after the PPT? What's the interview process like? What were the test pattern and interview experiences?

You'd ask seniors, get half answers, piece together something and still go in uncertain. When 700+ roles open in Phase 1 alone, no one person can collect reliable info on even a fraction of them.

So before graduating, my known has built Whistler; basically a searchable data archive of companies, roles, compensation, interview experiences, and selection processes from across batches which came in IITB in past years.

Think resobin, but for placements. Right now a few clubs release seniors resumes and interview experiences in fragments across drives and chats. The idea was to have all of it in one place, maintained and growing each year.

We've graduated now and don't want this to die. He is looking for a club or group within insti that wants to own this and keep it alive for future batches.

If you're a club member interested in taking this forward, dm.

reddit.com
u/Existing_Tea_3064 — 6 days ago