2/2
Incident 2: KTM ➔ HKG ➔ SFO
To bypass the transit mess of the first trip, we flew directly into Kathmandu this time. Surely, a direct flight out would bypass the red tape? Wrong. The roles simply reversed.
Arriving at Tribhuvan International Airport (KTM) for our return flight to the US via Hong Kong, I was hit with another roadblock. A small, physical sign at the check-in counter delivered the news: Any Indian national flying from Nepal to a third country requires a No Objection Certificate (NOC) from the Indian Embassy.
No warnings on travel portals. No notices during the airline booking process. Just a piece of paper taped to a terminal counter. Despite holding a valid US Green Card, the rule applied blindly. My wife was cleared to board; I was denied.
The Embassy Orbit & The VIP Fast-Track:
I finally managed to get the NOC, but the ordeal at the Indian Embassy in Kathmandu exposed the ugliest side of this administrative nightmare.
The waiting room was packed with people trapped in the exact same bureaucratic snare—entire families with young kids, stranded and exhausted, some waiting since 9:00 AM. The official staff and desk officers showed zero empathy, treating stranded citizens with a mix of cold indifference and hostility.
Yet, the classic dual reality of the system was on full display: while ordinary families spent agonizing hours pleading their case, others with the right "connections" and political clout walked in and walked out with their NOCs in under five minutes. If you have a VIP contact, the rules bend instantly; if you are a common citizen, you are an inconvenience.
The only saving grace was the support staff outside the main desks. Unlike the official bureaucrats, they were incredibly kind, helpful, and actually did their best to guide people through the chaos.
The Lazy Reality of Blanket Policymaking:
I understand the security or regulatory intent behind a rule like the NOC. It is likely meant to track people using Nepal as an unauthorized backdoor transit point out of India. But to catch that specific edge case, bureaucrats did what they always do: they issued a blunt, sweeping blanket rule instead of doing the hard operational work to filter it.
The rule would make logical sense if I had traveled overland from India into Nepal and was now trying to fly out to a third country. But that’s not my case. I am a permanent resident of the United States. I flew from the US, landed in Nepal, and am trying to fly back to the US.
To avoid the effort of building nuanced, conditional frameworks, bureaucrats simply pass 100% of the heavy lifting onto the citizens. They draft lazy, all-encompassing mandates without a shred of empathy or consideration for the people they disrupt.
When you require advanced AI tooling just to unearth the rules of your own citizenship—rules that the gate agents themselves don't even understand—the system is profoundly broken. The passport may give you global mobility, but the bureaucracy ensures you never quite leave the red tape behind.
1/2
The curse of Indian bureaucracy.
My wife holds a Nepali passport; I hold an Indian one. After a 3.5-year international travel hiatus while our US Green Cards were pending, we were finally cleared for liftoff. We planned to spend the next year making up for lost time, visiting family 2–3 times.
Instead, we ran face-first into the dizzying, uncoordinated reality of border bureaucracy—twice.
Incident 1: SFO ➔ HKG ➔ DEL
Two days before our Cathay Pacific flight, I did a routine check on our documentation. My AI agent, which tracks most of my life details, threw a flag: it said my wife needed an Indian visa.
Initially, I assumed it was an LLM hallucination. India and Nepal share a historic open-border treaty allowing freedom of movement without visas. I tried to look for the rule myself but couldn't find a trace of it on standard travel portals or mainstream sites.
It turned out the AI wasn't hallucinating; it had literally crawled and surfaced a single, obscure link buried deep within a government sub-page. The rule stated: "Nepali nationals arriving in India from or via Hong Kong, Taiwan, Macau, or Pakistan require a visa."
Because of our transit hub, my wife needed a visa just to land in Delhi. If it weren't for an AI agent digging through digital ruins, a human would have stood zero chance of finding this.
We scrambled. The Indian Consulate staff in the US were helpful and issued the visa just 24 hours before departure. We flew out relieved, thinking the hurdle was cleared.
The real absurdity happened at Delhi Immigration.
When my wife joined the foreign visa-holder queue, the immigration officers were completely baffled. They openly questioned why a Nepali citizen had an Indian visa, passing her passport around like a novelty item. It took 15 minutes of internal confusion for them to realize it was their own government's law—one they were actively supposed to know and enforce.
If Cathay Pacific hadn't strictly checked it at SFO gate control, no one at the arrival destination would have even noticed. It is peak incompetence: bureaucrats issue arbitrary directives without even notifying their own frontline officers.
@nalin1482@SnapmintEmi I am NOT Ravi Kumar. I don't live in India & this is a travel number I got in February for when I visit family in India.
Your support team has all this info (Ticket: 7794700645330) but literally told me to "continue making payments" for a random stranger's loan. Absolute clown show. Please get your house in order and stop this spam.
I feel sorry for anyone who's "Codex-pilled" or "Claude-pilled" and got brainwashed to hate on the other models / apps.
I constantly have Codex, Claude and Cursor Mac apps open, working together and in parallel.
They're all great, and each works well for different things.
Experimenting across these apps and leaning into each strength and special capabilities is a real treat this early in the game.
boris cherny goes on a podcast every three months and says something like “i’ve stopped breathing now i just wrote a breath.md” and the next day everyone in sf stops breathing
You can work 5 days a week and succeed as a startup.
Mercury has done that from day 0 and we are valued @ $5.2bn 7 years after launch.
I have been an entrepreneur for 20 years and raised 3 kids while doing it.
The point of success is to have a great life not just a startup 😊
I wanted OpenClaw to control my home.
Instead of building a Home Assistant plugin/skill/add-on, I made an agent-readable version of my HA dashboard and gave @openclaw the URL.
Now it can operate anything connected to HA: vacuum, car, AC, air purifiers, lights, automations, sensors, cameras, maps, etc.
The wild part: it does not just press buttons. It can inspect state, discover services, recover from failed calls, pull evidence, and verify outcomes.
curious what @steipete thinks: should more apps ship an agent-readable surface next to their human UI?
@_vmlops Yep, this is exactly why we built ClawLens for OpenClaw: local tool-call visibility, risk scoring, allow/deny/approval guardrails, Telegram approvals + audit trail.
Repo: https://t.co/HPxo0ICGoJ
Install: openclaw plugins install clawhub:@nk3750/openclaw-clawlens
This is exactly the layer ClawLens is trying to make visible.
Local audit trail for OpenClaw sessions/tool calls + risk scoring + attention queue, so repeated risky behavior can become block / approval / notify guardrails.
Install:
openclaw plugins install clawhub:@nk3750/openclaw-clawlens
Local first and open source: https://t.co/iBVc7A03vy
Once agents can search X, browse, and run tools, I really want a clean “what happened?” layer.
That’s why we built ClawLens — local dashboard for OpenClaw tool calls, sessions, risk signals, and guardrails.
openclaw plugins install clawhub:@nk3750/openclaw-clawlens
https://t.co/iBVc7A03vy
This makes agent activity way more powerful — and also makes observability and guardrails more important.
We built ClawLens for OpenClaw as a local flight recorder: sessions, tool calls, params, risk signals, audit trail, and guardrails.
openclaw plugins install clawhub:@nk3750/openclaw-clawlens
Crazy full-circle moment.
Stared at the default macOS Sonoma wallpaper today, had massive déjà vu, and dug through my old photos.
Turns out it’s the exact Kerala–Tamil Nadu border catchment area I rode through on my KTM back in 2018.
Guess Apple and I share the same taste in views 🌲
@OmarShahine@openclaw Love this direction. We just shipped ClawLens, an OpenClaw plugin that lines up with this: local visibility into agent/tool activity, risk scoring, audit trails, and optional guardrails at the tool-call boundary.
Repo: https://t.co/HPxo0ICGoJ
ClawHub: https://t.co/JOtaqrykkm
AI agents can now work for hours while you are away.
The hard part is seeing the work: which tools ran, what params were passed, which session it happened in, and what needs review.
We built ClawLens for OpenClaw: a local flight recorder for agent tool calls.
It shows sessions, tool params, risk scores, attention items, and audit history. From there, you can turn real behavior into guardrails: block, require approval, or allow with notification.
Install:
openclaw plugins install clawhub:@nk3750/openclaw-clawlens
If you run OpenClaw agents, I want blunt feedback: what visibility is still missing?
The basic workflow:
1. See every agent tool call in a local dashboard
2. Inspect the session, params, risk score, and audit trail
3. Spot repeated or risky behavior
4. Turn it into a guardrail
Guardrails can block, require approval, or allow + notify.
We are so back! 🔥 Codex 5.5 combined with OpenClaw is absolutely incredible. Huge shoutout to @steipete , @vincent_koc , @cherry_mx_reds , and the rest of the team for the amazing work!