Bitling

Small ideas. Brighter tomorrows.

Practice coding in your own environment.

Bitling takes a coding problem you find in the browser and turns it into a real local project, so you can solve it in the editor, terminal, and tools you already know.

See how it works

Chrome extension · coming soon

Bitling logo: a pixel-art chick hatching from an egg next to a small terminal

How it works

From a browser tab to your own editor.

No new IDE to learn. Bitling is the small bridge between where you find problems and where you like to work.

  1. Find a problem

    Browse a practice site the way you already do. Bitling starts with LeetCode, HackerRank, Codewars, Exercism, Codility's lessons, and Coderbyte.

  2. Send it local

    Open the Bitling extension on the problem page. It reads that page when you open it there, and not before.

  3. Get a real project

    Bitling writes a small project into a folder you pick: a README, a clean offline copy of the problem, starter code, and a test file.

  4. Practice your way

    Open it in your IDE, your terminal, your debugger. The solution files are yours, and Bitling never silently overwrites them.

>_ ~/Code/Practice/leetcode/two-sum
├── README.md
├── problem.html
├── build.gradle.kts
├── settings.gradle.kts
├── src/
│   ├── main/kotlin/Solution.kt
│   └── test/kotlin/SolutionTest.kt
└── .practice/
An example project in a folder you choose. The solution and test files are yours; Bitling looks after the README, problem.html, and .practice/. Open it in IntelliJ IDEA, VS Code, Cursor, or a terminal.

What's ready

Hatching one piece at a time.

Bitling is early. The browser extension comes first and is useful on its own. Each later piece builds on the one before it, and none of them are required.

  • Browser extension

    First up

    Captures a problem and writes a Kotlin + Gradle + JUnit project into a folder you choose. Works on its own, without the desktop app. Building the project needs a JDK and Gradle.

  • Desktop app

    Later

    A local library of the problems you've captured, one-click open in your IDE or terminal, and no folder picker each time. For macOS, Windows, and Linux.

  • Local coach

    Later

    Connect the AI tool you already use through a local MCP server. Hints start with a question and only reach the full answer when you ask for it.

  • Sessions and practice memory

    Later

    Timed practice sessions, a short reflection after each attempt, and gentle suggestions for what's worth revisiting.

  • Optional sync

    Later

    Carry your practice history between devices if you want to. Never required, you choose what goes, and your source code is never uploaded.

More sites (CodeSignal) are planned. Bitling isn't affiliated with any of the practice sites it works with.

Small promises

Built around your machine, not ours.

  • Local-first

    Your projects and practice data live on your computer. Bitling doesn't need an account, and it doesn't send your work anywhere.

  • Your code is yours

    Bitling tracks which files it generated and which you wrote, and never overwrites a file that's already yours.

  • Practice, not assessments

    Bitling is built for practice. It's designed to step aside on proctored or employer assessment pages, like Codility's hiring tests.

  • No tracking

    No telemetry by default, and no trackers on this site.

Read the privacy page for how Bitling handles your data.

Little wins stack up.

Bitling isn't available to install yet. Links will show up here when each piece is ready.

  • Chrome extension Coming soon
  • Desktop app for macOS, Windows, and Linux Later