I made loopy because I'm tired of there being a new trend telling me im using claude code wrong every 3 weeks, and I wanted something that can persistently analyze my usage and suggest ways to just use it better (save time, tokens, or increase quality)

  loopy runs quietly in the background, watches session transcripts, recognizes patterns and proposes ready-to-install
  automation loops. you review them in the loopy terminal and approve what makes sense for you.

  Loopy will update periodically to reflect the next "meta" of skills, loops etc in the CC/Codex community. Right now, the
  trend is on loop engineering and I think this is one that'll stay for sometime.

  Loopy is also fully aware of the capabilities of CC/Codex and will update as new features come out like "/goal" or
  dynamic workflows, to leverage those inside your next meta-sugestion.


  The pipeline: a launchd watcher notices new transcripts → a digester compresses and redacts them → an engine sends them
  to your own claude -p binary and looks for recurring patterns → good candidates land as proposals in your inbox.

  its completely free, no cloud, no sub, no api; I'm doing it for the love of the game.

  with loopy; your (and mine) claude code and codex usage methods will no longer be out dated, no one will ever shame you
  because you don't know the next hack, and no trend on X will ever make you feel fomo again.

  also i added /fable so you can force any model to run with fable's system prompt. Easter EGG!!!