Lumaline Concept · not built yet Answer 2 questions →

Would you install this?

One line of advertising,
where you're already looking.

While the agent thinks, you stare at a spinner. Lumaline would put a single quiet line of sponsorship there — and nothing else, anywhere, ever. That's the whole idea. Before writing a line of it, we want to know if you'd actually use it.

~/work/payments — agent session
> refactor the auth middleware onto the new session store
 
I'll start by reading the current middleware.
⎿ Read src/middleware/auth.ts (142 lines)
⎿ Read src/session/store.ts (88 lines)
 
Rewriting the token lookup
 
Working… (18s · ↑ 2.4k tokens · esc to interrupt)
ad Hexbase · Postgres branches for every pull request · hexbase.dev

Mock-up. The sponsors above are invented placeholders, not real advertisers.

The rules it would ship with

Where

The spinner line only

One line, under the status row, while you're waiting anyway. Never in your output, your diffs, your commits, or a popup. It disappears the moment the agent finishes.

Privacy

Your prompts stay put

No prompt text, no file contents, no repo names leave your machine. Ads would be fetched in bulk and picked locally — the server never learns what you're building.

Price

Free, and ads are why

The free tier stays free because sponsors pay for it. If that trade is a bad deal for you, the questions below are where you say so.

Two questions. No wrong answers.

Honest "no" answers are worth more to us than polite yeses — a no here saves months of building the wrong thing.

01A free CLI companion that shows one line of ads while the agent works — would you install it?
02How does an ad on the spinner line actually land for you?

Only if you want a ping when there's something to try. Leave it blank and your answers still count.