$ whoami
VP Engineering @ KnackLabs (part of CAW Studios). Hyderabad.
I build AI agent infrastructure. Identity protocols. Cross-platform messaging. MCP contributor. Rust when it matters. TypeScript when it doesn't. LangChain Ambassador on the side.
I run an AI assistant from a spare MacBook that manages my LinkedIn, reviews my code, screens CVs, finds leads, and occasionally roasts my bad decisions.
$ cat /proc/current
Clawdentity — cryptographic identity + secure messaging for AI agents. Per-agent DIDs, Ed25519 signing, WebSocket relay, cross-platform webhooks. 12K lines of Rust. 70 tests. IETF Internet-Draft published. Works on OpenClaw, PicoClaw, NanoBot, NanoClaw. One binary. Zero deps.
$ ls ~/projects --sort=stars
| Project | What | Stars |
|---|---|---|
| firecrawl-mcp-server | Web scraping for AI assistants. Led initial implementation. |  |
| langchainjs-mcp-adapters | MCP ↔ LangChain bridge. Contributor. |  |
| clawdentity | Agent identity protocol + Rust CLI. |  |
$ cat /etc/opinions
- Small fine-tuned models on tool calling > generic large models for most workflows
- Nobody talks about the interface problem. Your agent is smart. Your users don't know what to ask.
- Everyone demos. Nobody ships. It breaks at the boring stuff — config, auth, retries, edge cases.
- Data quality > model size. Always.
- CLI agents are general-purpose. Not "coding tools."
$ uname -a
$ history | tail -5
- Published Clawdentity IETF Internet-Draft (RFC for agent identity)
- Built Rust CLI — single binary for 4 agent platforms
- Opened webhook PRs to PicoClaw, NanoBot, NanoClaw
- Running 15+ automated cron jobs from an AI assistant on WhatsApp
- Shipped ravi.sh (brutalist portfolio, because LinkedIn profiles are boring)
