brian austin

Posted on Apr 24

You cancelled your Claude subscription. Now what? (a practical guide with code)

#webdev #ai #node #discuss

You cancelled your Claude subscription. Now what?

HN had a thread this week titled 'I Cancelled Claude' that got 392 upvotes and 208 comments. Most of the comments were variations of: same, but I don't know what to use instead.

I cancelled my Claude Pro subscription 3 months ago. Here's what I actually replaced it with, and the exact code I use.

Why people are cancelling

The pattern is consistent across the HN comments:

Token limits — Claude Pro's 5-hour reset windows and opaque limits make it unreliable for production workflows
Quality regressions — Anthropic literally published a postmortem about Claude Code quality regressions (April 2026)
Price creep — $20/month base, $100/month for Teams, $200+/month for API at real usage volumes
The treadmill — GPT-5.5 dropped this week. DeepSeek v4 dropped this week. You're always one launch behind.

The problem isn't Claude specifically. It's the subscription model for AI at this stage of the technology.

What I actually use now

I use a flat-rate Claude API wrapper at $2/month. No token counting. No usage limits. Same Claude model underneath.

Here's the curl command:

curl -X POST https://api.simplylouie.com/api/chat \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message": "explain async/await in JavaScript"}'

Returns:

{
  "response": "Async/await is syntactic sugar over Promises...",
  "model": "claude-3-5-sonnet",
  "usage": "unlimited"
}

No input_tokens. No output_tokens. No invoice at the end of the month.

The migration from Claude Pro

If you were using Claude Pro's web interface for development work, the migration path is:

Step 1: Find your actual use cases

Before migrating, log what you actually use Claude for. For me it was:

Explaining unfamiliar code (~40% of usage)
Writing boilerplate (~30%)
Debugging logic errors (~20%)
Summarizing documentation (~10%)

Step 2: Build a thin wrapper

Instead of using the web interface, build a small local tool that fits your workflow:

// claude-local.js — run from terminal
const readline = require('readline');
const https = require('https');

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout
});

function ask(message) {
  return new Promise((resolve) => {
    const data = JSON.stringify({ message });

    const options = {
      hostname: 'api.simplylouie.com',
      path: '/api/chat',
      method: 'POST',
      headers: {
        'Authorization': 'Bearer YOUR_API_KEY',
        'Content-Type': 'application/json',
        'Content-Length': data.length
      }
    };

    const req = https.request(options, (res) => {
      let body = '';
      res.on('data', chunk => body += chunk);
      res.on('end', () => {
        const parsed = JSON.parse(body);
        console.log('\n' + parsed.response + '\n');
        resolve();
      });
    });

    req.write(data);
    req.end();
  });
}

async function main() {
  console.log('Claude terminal (type exit to quit)\n');

  const loop = () => {
    rl.question('You: ', async (input) => {
      if (input === 'exit') { rl.close(); return; }
      await ask(input);
      loop();
    });
  };

  loop();
}

main();

Run it with node claude-local.js. Same experience as the web interface, but from your terminal, and the bill is fixed.

Step 3: Add it to your editor

If you use VS Code, add a keybinding that sends selected code to Claude:

// keybindings.json
{
  "key": "ctrl+shift+a",
  "command": "workbench.action.terminal.sendSequence",
  "args": {
    "text": "node ~/claude-local.js\n"
  }
}

Not as polished as Cursor or Claude Code. But you own it, and the bill doesn't change.

The honest tradeoffs

What you lose:

Artifacts (Claude's canvas-style document editor)
Projects (persistent context folders)
The polished web UI
Claude Code integration

What you gain:

Fixed monthly cost ($2 vs $20)
No 5-hour reset windows
Works in scripts and automation
Not affected by Claude Pro quality regressions
No anxiety about usage

For most developers doing code assistance, the things you lose are UI conveniences. The core capability — the language model itself — is unchanged.

Why this week specifically

GPT-5.5 launched this week. DeepSeek v4 launched this week. If you're on Claude Pro, you're paying $20/month for a product that Anthropic is actively racing to keep competitive with two new models simultaneously.

The flat-rate wrapper doesn't care which model wins. It exposes Claude's API. When Anthropic ships a better model, it becomes available. You pay the same $2.

The question I'm genuinely curious about

For those who cancelled Claude Pro (or are thinking about it): what's the one feature you'd miss most?

I expected it to be Artifacts. It turned out to be Projects — the persistent context folders. I had to rebuild that with a simple JSON file locally, which took about 30 minutes but works fine.

What's your answer? That probably tells you whether a DIY setup makes sense for your workflow.

The flat-rate API wrapper I use is SimplyLouie — $2/month, no token limits, 50% of revenue goes to animal rescue. API docs at simplylouie.com/developers.

DEV Community