Rishab Ramanathan

founder / CTO @openlayerco

[Rishab Ramanathan @rishramanathan]

1/ 🧵The AI revolution can progress exponentially faster if we overcome one major challenge: the reliability problem. Ensuring consistently safe and functional outcomes across real-world scenarios is a mighty task for today’s AI teams.

[Rishab Ramanathan @rishramanathan]

@vitorviesi @octolane @coffeewithone @halim__rafi @yashsehgaldev good stuff @vitor!

[Gustavo Cid @_cgustavo]

We were tired of manually writing git commits for @linear issues. So I built a @raycast extension.

Simply copy the Linear issue ID → hit your hotkey → paste the commit message.

That's it!

Why build it?

We love how you can link Git commits to @linear issues. However, doing this while also following other best practices (like Conventional Commits) made writing commit messages painful.

For example, for a Linear issue with ID 'ENG-123' and title 'Some bug', we'd have to:

1. Type the commit type ('fix')
2. Copy the Linear issue ID from Linear
3. Paste it with 'closes' (or some other magic word) → 'fix(closes ENG-123):'
4. Copy the Linear issue title from Linear
5. Paste it → 'fix(closes ENG-123): Some bug'
6. Lowercase the first letter → 'fix(closes ENG-123): some bug'

We'd bounce between Linear and Terminal 3+ times, copying/pasting/editing until we got it right.

The team was rightfully complaining that the process was annoying. We even considered changing how we name Linear issues to minimize the number of edits.

That's why I built the @raycast extension!

Behind the scenes, the extension fetches the Linear issue with the specified ID using Linear's API and constructs the full commit command. The conventional commit type ('fix', 'chore', 'docs', etc.) is inferred from the Linear issue label.

The extension is private to the @openlayerco org, because it follows our commit message formatting, but hopefully you can build your own version of this!

[Rishab Ramanathan @rishramanathan]

@_cgustavo @linear @raycast will quickly become my most used raycast shortcut

[Openlayer @openlayerco]

Chicago AI/ML leaders — join us Aug 7 for a private Topgolf night

🍸 Drinks & bites
🧠 10-min talk: “Catching GenAI failures before prod”
🎯 Good swings, better convos
🎟️ Space is limited → [Request Invite] 👇

https://t.co/EymmJUm1uS

[Openlayer @openlayerco]

Say hello to Emmett Nelson, Openlayer’s newest Account Exec! From AWS to Metaplane to Openlayer, he’s seen it all in AI/ML sales.

Why he joined, how he stays sharp, and his favorite 2025 photo 👇https://t.co/yXBX7xPunZ

[Openlayer @openlayerco]

At #DataAISummit, teams echoed the same concern:

Hallucinations, chain failures, degraded prompts, LLMs in prod are breaking without visibility.

Openlayer helps you catch it before it hits users.
🔗 https://t.co/6XJ5t6pntI

[Openlayer @openlayerco]

It’s Friday.
Your pipeline says it’s “fine.”
Your model says it “should work.”
Your LLM is feeling ✨creative✨
Openlayer helps you trust what you ship, before it bites back.
🔗https://t.co/fQ5rOjDFZn

[Openlayer @openlayerco]

We’re heading to @databricks #DataAISummit (June 9–12)! We’ll be on-site all week connecting with teams building GenAI & ensuring their AI systems are reliable + prod-ready. Booth info drops May 30. Swag? 🔥

[Openlayer @openlayerco]

Observability = understanding model behavior, not just metrics. Is your AI observable? https://t.co/YaCxJdIjvd

[Openlayer @openlayerco]

What’s your biggest challenge with AI deployments?

[Openlayer @openlayerco]

@jpmorgan nailed it: AI speed without safeguards = big risks. Openlayer helps teams deploy AI safely—with governance, explainability, and evaluation.#AIgovernance #ExplainableAI #ModelSecurity

https://t.co/3fLTETcY2K

[Rishab Ramanathan @rishramanathan]

@_cgustavo magical indeed

[Gustavo Cid @_cgustavo]

My first magical moment with LLMs was using GPT 3.5. My second was MCP.

That's why I'm super excited about the Openlayer MCP server release!

Check out the demo below

[Rishab Ramanathan @rishramanathan]

@vitorviesi @openlayerco @ericaoutput @vikaaaaaaaaas @guilherme_rodz @nucleoicons date picking never felt sweeter

[Rishab Ramanathan @rishramanathan]

@openlayerco @guilherme_rodz 🚀🚀🚀

[Rishab Ramanathan @rishramanathan]

@vitorviesi @openlayerco @ericaoutput @vikaaaaaaaaas @guilherme_rodz @nucleoicons unstoppable ⚒

[Rishab Ramanathan @rishramanathan]

@vitorviesi @openlayerco @ericaoutput @vikaaaaaaaaas @guilherme_rodz @nucleoicons 😍😍

[Rishab Ramanathan @rishramanathan]

@vitorviesi @openlayer @ericaoutput @vikaaaaaaaaas @guilherme_rodz @openlayerco @nucleoicons 🤩

[Vitor @vitorviesi]

Every detail, refined for light and dark. ⚒️🌓
Menu designs, built for @openlayer.
With the amazing @ericaoutput @vikaaaaaaaaas @guilherme_rodz

[Rishab Ramanathan @rishramanathan]

4/ Our mission at Openlayer is to operationalize a system of continuous governance, allowing AI systems to evolve alongside their guiding principles. Here’s the full post with a more detailed breakdown on how we arrived at this framework 👇
https://t.co/1aq9emWMXg

[Rishab Ramanathan @rishramanathan]

1/ 🧵The AI revolution can progress exponentially faster if we overcome one major challenge: the reliability problem. Ensuring consistently safe and functional outcomes across real-world scenarios is a mighty task for today’s AI teams.

[Rishab Ramanathan @rishramanathan]

3/ The only real solution to the reliability problem is a governance-inspired approach—exactly like how societies rely on constitutions to guide human behavior. Think about some of the different “constitutions” we rely on:

The United Nations charter.
The Declaration of Independence and the Bill of Rights.
Regulatory codes in different industries (e.g. finance, pharma, energy, telecom, agriculture).
Company charters and mission statements.
Reddit forum guidelines.