Idlen - Earn while you work with AI in any IDE or browser
by•
Developers wait on AI all day. That wait is an ad slot. One network, three doors.
If you code: install the VS Code, Cursor or Chrome extension. A native ad while the model thinks. You keep 70%. We don't read your prompts.
If you sell a developer tool: you show up in the IDE and the browser, targeted by the stack they actually use (React, Python, AWS). Pay €200, get €400 this week.
If you shipped a chat app: npm i @idlen/chat-sdk. Three lines. Ads optional. No key, no ads. You keep 70%.
Replies
Idlen
Maker here.
I got tired of ads that pretend developers hang out on LinkedIn. They hang out in the editor, in the browser tab waiting on Claude, or in the chat app someone shipped last month.
Idlen is one network, three doors.
1. You code: VS Code / Cursor / Chrome extension. Ads while the model thinks. You keep 70%. Prompts stay on your machine.
2. You sell a tool: you buy that slot. Targeting is the real stack, not a persona. Pay €200, get €400 this week.
3. You built a ChatGPT-style app: npm i @idlen/chat-sdk. Three lines. Ads off until you put a key in.
Video is 50 seconds, one pass per door.
If you try it, tell me which door and what broke. I'll be in the comments today.
idlen.io
Keeping 70% of the ad revenue makes this more interesting for developers. If the ads stay relevant and unobtrusive I could see this working well.
Idlen
@james_wilson60 That's the bet. 70% is the actual split, not a launch number.
Relevant means the stack in the repo, not a persona. Unobtrusive means a card while the model thinks, not something in your code. Formats and cooldown are yours.
If you try the extension and an ad is loud or off, tell me which one. That's the part I want to hear.
I like the privacy angle here, especially the point about not reading prompts. That's important when developers are working with private code or company data.
Idlen
@iris_carr That's the line we won't cross.
The extension never sends the prompt or the file you're editing. Targeting is the stack on disk: package.json, go.mod, that kind of file. Not the code, not the comments, not what you typed to the model.
If you're on a work repo, that's the whole point. Company data stays on the machine.