Show HN: Lotas – Cursor for RStudio

Hacker News (score: 18)
Found: July 21, 2025
ID: 427

Description

IDE/Editor
Show HN: Lotas – Cursor for RStudio Hey HN! We’re Jorge and Will from Lotas (https://www.lotas.ai/), and we’ve built an AI coding assistant into RStudio (think Cursor for RStudio).

RStudio is used by about 2 million data scientists and academics, but they currently lack a coding assistant within their IDE. Developers in other environments benefit from tools like Cursor and Windsurf, but R users don’t have any equivalent tools to speed up their workflow. Since ~80% of R programmers prefer to use RStudio over other IDEs like VSCode to write R code, we figured a tool like this one could be quite useful.

Both of us were PhD students at Harvard. Jorge was in the biophysics program and Will was in the biostatistics program where most people used RStudio every day. We saw how integrated code assistants were taking off in other IDEs, but we noticed that the RStudio integrations were still lagging far behind. Many R users were copying and pasting code from ChatGPT to build their workflows, and this was clearly slow and fragile.

To bring the Cursor-like experience to RStudio users, we built Rao (https://www.lotas.ai/): a fork of RStudio with an embedded AI assistant that is aware of the user’s local context (both files and variable environment), can read and write files, can run code or commands, and can interpret textual or visual output. It works with any of the file formats already in RStudio (R, notebooks including RMDs and QMDs, Python, Stan, etc.), allowing R programmers to iteratively perform entire data analyses inside their preferred IDE.

Other AI data science tools are either (1) built on the web or in environments people don’t already use, (2) are completely focused on python notebooks, or (3) are weak package-based assistants with limited functionality. Rao is exactly like the RStudio IDE that millions of data scientists already use, but it incorporates a powerful AI assistant and works with all the standard file types.

You can download Rao at https://www.lotas.ai/download, watch our demo on the homepage (https://www.lotas.ai/), and work through some example use cases on our GitHub (https://github.com/lotas-ai/rao/tree/main/demos). We have a one-week free trial (no card required) and provide 500 queries/month for $20/month after that. We’d love to hear feedback from the HN community to make Rao as useful as possible! You can reach us at founders@lotas.ai.

P.S. We have zero data retention (ZDR) agreements with OpenAI and Anthropic, but we currently recommend users do not input sensitive or regulated data like PHI into Rao until we sign BAAs with both model providers. For more information on our security practices, please visit the security page on our website https://www.lotas.ai/security.

More from Hacker

Show HN: Tusk Drift – Turn production traffic into API tests

Show HN: Tusk Drift – Turn production traffic into API tests Hi HN! In the past few months my team and I have been working on Tusk Drift, a system that records real API traffic from your service, then replays those requests as deterministic tests. Outbound I&#x2F;O (databases, HTTP calls, etc.) gets automatically mocked using the recorded data.<p>Problem we&#x27;re trying to solve: Writing API tests is tedious, and hand-written mocks drift from reality. We wanted tests that stay realistic because they come from real traffic.<p>versus mocking libraries: Tools like VCR&#x2F;Nock intercept HTTP within your tests. Tusk Drift records full request&#x2F;response traces externally (HTTP, DB, Redis, etc.) and replays them against your running service, no test code or fixtures to write&#x2F;maintain.<p>How it works:<p>1. Add a lightweight SDK (we currently support Python and Node.js)<p>2. Record traffic in any environment.<p>3. Run `tusk run`, the CLI sandboxes your service and serves mocks via Unix socket<p>We run this in CI on every PR. Also been using it as a test harness for AI coding agents, they can make changes, run `tusk run`, and get immediate feedback without needing live dependencies.<p>Source: <a href="https:&#x2F;&#x2F;github.com&#x2F;Use-Tusk&#x2F;tusk-drift-cli" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Use-Tusk&#x2F;tusk-drift-cli</a><p>Demo: <a href="https:&#x2F;&#x2F;github.com&#x2F;Use-Tusk&#x2F;drift-node-demo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Use-Tusk&#x2F;drift-node-demo</a><p>Happy to answer questions!

Show HN: Yolobox – Run AI coding agents with full sudo without nuking home dir

Show HN: Yolobox – Run AI coding agents with full sudo without nuking home dir

Sandbox: Run untrusted AI code safely, fast

Sandbox: Run untrusted AI code safely, fast

Show HN: Bithoven – A high-level, imperative language for Bitcoin Smart Contract

Show HN: Bithoven – A high-level, imperative language for Bitcoin Smart Contract Hey HN! I’m a researcher working on Bitcoin smart contracts, and today I’m releasing Bithoven—a high-level imperative language that compiles to native Bitcoin Script (Legacy, SegWit, and Taproot).<p>The Goal:<p>Raw Bitcoin Script is notoriously difficult to reason about. Writing raw Bitcoin Script today feels like writing Assembly in the 1970s. You have to mentally juggle the stack (`OP_SWAP`, `OP_ROT`), manually manage distinct execution branches, and pray you didn&#x27;t leave a stack item unconsumed (which crashes the script). My goal was to bridge the gap between complex contract logic and raw opcodes, allowing developers to write readable, compile-time-safe code.<p>Key Features:<p>- Imperative Syntax: Write logic using familiar if&#x2F;else and return statements instead of mental stack juggling.<p>- Type Safety: First-class support for bool, signature, string, and number types to prevent runtime errors.<p>- Targeted Compilation: Support for Legacy, SegWit, and Taproot compilation targets.<p>- Native Primitives: Built-in keywords for timelocks (older, after) and cryptography (sha256, checksig).<p>You can try it in the browser here (runs via WASM): <a href="https:&#x2F;&#x2F;bithoven-lang.github.io&#x2F;bithoven&#x2F;ide&#x2F;" rel="nofollow">https:&#x2F;&#x2F;bithoven-lang.github.io&#x2F;bithoven&#x2F;ide&#x2F;</a><p>Here is an example of a Hashed Time-Locked Contract (HTLC):<p><pre><code> (condition: bool, sig_alice: signature) (condition: bool, preimage: string, sig_bob: signature) { if condition { &#x2F;&#x2F; Relative locktime (Sequence) older 1000; return checksig (sig_alice, alice_pk); } else { &#x2F;&#x2F; Hashlock verification verify sha256 sha256 preimage == hash; return checksig (sig_bob, bob_pk); } } </code></pre> The project is free open source and the academic paper is currently under review. I’d love to hear any feedback. Thanks for checking it out!

No other tools from this source yet.