Triple Citrus Cake | Made by Meaghan Moineau

A few weekends ago, I had one of those mornings where you wake up craving something fresh and sunny to get your day going. It was gray and drizzly outside, and I wanted to bring a bit of brightness into the day. As I scanned my pantry, I spotted a forgotten lime yogurt, an orange rolling around with a couple of lemons in the fruit drawer, and a plan began to form. This Triple Citrus Cake is the kind of bake that feels like an instant mood-lifter. It’s got that perfect balance of tangy and sweet, and it’s way simpler than it sounds. Plus, it’s the kind of cake where you might already have most of the ingredients just hanging around. Every bite is like a little burst of sunshine, which sometimes is just what you need.

Jump to Recipe

What You’ll Need

Let me tell you, the best part about this ingredient list is that it’s the kind of thing you probably already have on hand. Here’s what you’ll need to create your own slice of citrusy heaven:

  • 1 1/2 cups flour
  • 2 teaspoons baking powder
  • 1/2 teaspoon salt
  • 3/4 cup lime yogurt
  • 1 cup sugar
  • 3 whole eggs
  • 1 teaspoon vanilla extract
  • 1/2 cup grapeseed oil
  • Zest of 1 lemon
  • 1/4 cup orange juice
  • 1 cup powdered sugar

How to Make Triple Citrus Cake

  1. Preheat your oven to 350 degrees. You want it nice and warm, ready to give your cake a cozy bake.
  2. In a medium bowl, whisk together the flour, baking powder, and salt. This is your dry team; they’ll hang out together until called.
  3. Grab your electric mixer and in a larger bowl, beat together the lime yogurt, eggs, sugar, vanilla, oil, and lemon zest. It’ll look silky smooth and smell divine.
  4. Gently fold the dry ingredients into the wet mixture using a spatula. You’re aiming for a batter that’s just combined; over-mixing is a no-go here.
  5. Coat a 9 x 5 loaf pan with floured baking spray or line with parchment paper and spray. Pour the batter in, smoothing the top so it’s even.
  6. Bake for 40-50 minutes, or until a cake tester comes out clean. The top will be golden brown and your kitchen will smell like citrus heaven.
  7. Let the cake cool in the pan for at least an hour. Patience, my friend. The wait is worth it.
  8. Once cool, transfer to a serving plate. Mix the powdered sugar with orange juice until you have a smooth glaze, then drizzle it over the cake. Watch as it glistens invitingly.

Cook’s Notes

When it comes to baking, patience is key, especially in letting the cake cool before you apply the glaze. Trust me, you don’t want to rush it or you’ll end up with a soggy mess. The cake keeps well for 3-4 days if covered tightly and stored at room temperature, though I doubt it’ll last that long! If you’re planning to make it ahead, bake the cake and store the glaze separately. Glaze just before serving for the best texture.

Make It Your Own

Looking to switch things up? Here are a few ideas:

  • Swap the lime yogurt for Greek yogurt and add a bit more lemon zest for an extra lemony punch.
  • Replace grapeseed oil with melted coconut oil for a subtle coconut twist.
  • Add a handful of poppy seeds to the batter for a delightful texture and a bit of visual flair.
  • Use a mix of blood orange juice for the glaze if you want a richer color and slightly different taste.

If you try this, I’d love to hear how it turns out — drop a comment or tag me in your cake pics! It always makes my day to see your creations. Happy baking! 🍋🍊🍋

Related update: Triple Citrus Cake

Related update: Roasted Strawberry Coconut Milk Ice Cream

Google Triples Gemini Antigravity Limits | Analysis by Brian Moineau

TL;DR

  • Google tripled Gemini usage limits for Antigravity twice in one week after developers hit caps within hours; other Gemini Apps surfaces kept tighter quotas. [1]
  • This is not generosity; it’s a live-fire test of compute-based metering for agentic dev tools that Google will extend and harden across Gemini Apps, Cloud, and Antigravity in 2026. [1][2][3]
  • Rivals (GitHub Copilot and AWS Q Developer) are shipping the same playbook—rate limits, usage credits, and request-based billing—so quota-aware workflows are now table stakes. [4][5][6]

What the source said

9to5Google reported during the week of Google I/O 2026 that Google introduced compute-based usage limits for Gemini and then raised Antigravity’s ceilings twice—first a 3× rate-limit increase and later a 3× weekly quota bump—after users hit caps within a few hours of work. Varun Mohan of Google DeepMind said some users reached the weekly limit “after a couple work sessions,” and Google reset paid-plan quotas two times in the same week. The site added that post-reset quotas remained below prior levels and that increases applied only to Antigravity, not to other Gemini Apps surfaces like web or mobile. [1]

Why it matters

Google Antigravity is the agent-first developer suite—CLI, desktop app, and orchestration layer—pitched at Google I/O 2026 as “agents that do work,” not just chat. Caps that bite during compile–test–debug loops jeopardize the IDE of record and erode trust on day 1 of an agent pitch. Teams that adopted Antigravity 2.0 following the I/O keynote now face a quota regime that can interrupt multi-step sessions mid-sprint. [2][7]

The people who feel the blast radius aren’t only individual coders. They include SRE leads forecasting throughput for Q3 2026, procurement managers matching AI spend to monthly budgets in USD, and vendors like JetBrains or the VS Code marketplace whose extensions fail if an agent loop ends early. The fact that Google raised Antigravity limits twice while leaving other Gemini surfaces unchanged signals a priority: keep developer stickiness in the IDE hub where session economics matter most. [1][3]

Original analysis

Contrarian read

  • Consensus: Two quota hikes in one week show that Google listened, and the worst is over.
  • My take: The hikes are a pressure release, not a reversal. Google is normalizing compute-based metering because agent loops are bursty and costly; Antigravity merely hit the wall first. Gemini access already hinges on plan-bound limits, and Cloud services publish quota regimes; expect more explicit meters, not fewer, through 2026. [3][7]

Why? Major rivals are aligning revenue to inference cost. GitHub begins request-based Copilot billing on June 1, 2026 and documents rate limits by surface. AWS Q Developer lists concrete service quotas per account and region. The industry favors quotas because they curb runaway loops and create predictable upsell ladders across Pro, Business, and Enterprise tiers. [5][6][4]

Back-of-envelope: the “lockout tax” on a team

Assumptions (midsize product group in the US):

  • Fully loaded developer cost: $120/hour.
  • Antigravity weekly limit hit “after a couple work sessions,” forcing context rebuilds, tool re-wiring, or model swapping; assume 15 minutes of friction per lockout per engineer. [1]
  • Ten engineers rely on Antigravity for code generation, refactors, and agent tasks; each hits one friction event per week.

Math (shown):

  • 0.25 hours × $120/hour = $30 friction per engineer per event.
  • $30 × 10 engineers = $300/week.
  • If two events per week before the second reset, that’s ~$600/week.
  • $600/week × 52 weeks ≈ $31,200/year.

Even if the second quota increase halves the friction, you still pay a five-figure ($10k+) annual “lockout tax” unless you add quota-aware automation—e.g., route to a backup model when Antigravity nears its ceiling or shift longer loops to off-peak/cloud jobs with batch scheduling. The exact number varies, but the slope is clear: invisible ceilings become silent productivity losses that compound. [1]

2x2: Who tolerates Gemini usage limits for Antigravity?

  • Budget high, tolerance high: S&P 500 engineering orgs and big tech platforms. They’ll buy higher tiers or negotiate enterprise quotas and SLOs; the risk is hidden throttling on new agent behaviors until contracts land. [6]
  • Budget high, tolerance low: YC and Series B startups in launch weeks. They’ll multi-home across Gemini, Copilot, and Claude; a single mid-sprint lockout pushes vendor diversification within 24 hours. [4][5]
  • Budget low, tolerance high: GitHub Student Pack users and hobbyists. They’ll live with caps but practice “quota hygiene” (shorter sessions, fewer tool calls) and push bulk tasks to cheaper or local options. [3]
  • Budget low, tolerance low: One-person US consultancies on fixed-fee milestones. They’ll switch IDE agents or plugins the first time a quota blocks a client deadline.

Named-stakeholder breakdown

  • Google: Keep Antigravity credible as the agentic coding cockpit announced at I/O 2026. Ship visible meters, predictable resets, and paid expansion paths that never strand a session mid-loop. [2][3]
  • GitHub (Copilot): The June 1, 2026 request-based billing shift lowers the PR cost of Google’s caps—“everyone’s doing it”—but raises expectations for in-IDE transparency and dashboards. [5][4]
  • AWS (Q Developer): Quota-first culture is an advantage; documented limits with knobs look safer to CIOs who want predictable spend and throughput. [6]
  • Tool vendors (JetBrains, VS Code extensions): Build quota-aware orchestration (retry/backoff + model failover) so long-running agent runs don’t collapse at 95% completion.
  • Team leads/procurement: Push for multi-vendor agent stacks and SLAs with concrete daily/weekly and per-session ceilings rather than vague “fair use.” [6][4]

What others are missing

The real unit of value is shifting from tokens to agent sessions in the IDE. Antigravity runs a loop of code edits, test runs, file ops, and tool invocations; a weekly token pool hides the cost shape of that loop. A cap that feels roomy for chat can choke a refactor+test+debug cycle in VS Code or JetBrains. That’s why Google raised Antigravity limits while leaving other Gemini surfaces unchanged: session economics bite first in the IDE, which needs session-oriented quotas and in-IDE telemetry to prevent brittle loops. [1][2][3]

What to watch next

  1. By June 30, 2026, Google will publish explicit per-tier Antigravity numeric ceilings (daily and weekly) and ship an in-product “quota meter” in the Antigravity UI or CLI release notes; you can verify this in public docs and changelogs. [2]

  2. By September 30, 2026, GitHub will add an in-IDE Copilot quota dashboard for Pro/Business that shows remaining weekly/monthly usage and reset times, confirmed via VS Code or JetBrains extension changelogs. [5][4]

  3. By Q4 2026, at least one mainstream IDE or agent framework will ship automatic “quota-aware scheduling” (defer/route/shorten loops near cap) with documented support for Google Antigravity and one rival such as Copilot or AWS Q Developer. [6][4]

My take

Raising Antigravity limits twice was the right triage in May 2026, but the message is louder than the move: agent work costs real compute, so quotas are product strategy. If Google wants developers to live in Antigravity, quotas must become a first-class UX surface—clear meters, graceful degradation, and paid escape hatches that never dead-end a sprint. Otherwise, Copilot’s request-based world and AWS’s quota-first culture will peel off teams that prize predictability in 2026 and 2027. The winners will be the tools that make quotas boring. [1][5][6]

Sources

  1. Google has tripled Gemini usage limits for Antigravity, twice — 9to5Google (https://9to5google.com/2026/05/21/google-has-tripled-gemini-usage-limits-for-antigravity-twice/) — Details the two 3× increases, user lockouts, and Varun Mohan’s quota resets during I/O week.

  2. All the news from the Google I/O 2026 Developer keynote — Google Developers Blog (https://developers.googleblog.com/all-the-news-from-the-google-io-2026-developer-keynote/) — Confirms Antigravity as Google’s agent-first developer platform introduced at I/O 2026.

  3. Gemini Apps limits & upgrades for Google AI subscribers — Google Support (https://support.google.com/gemini/answer/16275805?hl=en) — Documents plan-bound Gemini access and the existence of usage limits across tiers.

  4. Usage limits for GitHub Copilot — GitHub Docs (https://docs.github.com/en/enterprise-cloud%40latest/copilot/concepts/rate-limits) — Explains Copilot rate limits and guidance when users hit them.

  5. Requests in GitHub Copilot (usage-based billing) — GitHub Docs (https://docs.github.com/en/copilot/concepts/billing/copilot-requests) — States Copilot’s move to request-based, usage-linked billing starting June 1, 2026.

  6. Amazon Q Developer endpoints and quotas — AWS General Reference (https://docs.aws.amazon.com/general/latest/gr/amazonqdev.html) — Lists Q Developer service quotas and regions, illustrating quota-first design in rival tooling.

  7. Google is making Gemini CLI users switch to its new Antigravity 2.0 — TechRadar Pro (https://www.techradar.com/pro/google-is-making-gemini-cli-users-switch-to-its-new-antigravity-2-0-so-what-will-it-mean-for-you) — Independent coverage of Antigravity 2.0 (CLI and SDK) around the I/O 2026 timeframe.

Fat Free Gingerbread Cookies | Made by Meaghan Moineau

The other day, I found myself in one of those classic kitchen dilemmas. It was a chilly autumn afternoon, I was craving something warm and spicy, and I swear, every recipe I came across called for ingredients I didn’t have on hand. Determined not to let my sweet tooth win, I started rummaging through my pantry, and that’s when it hit me: fat-free gingerbread cookies! Yes, you read that right. These cookies are just what you need when you crave that cozy, ginger-spiced goodness but want to keep things light. Trust me, these cookies are packed with bold flavors, and you might already have most of these ingredients at home. Plus, they’re soft, chewy, and perfect for an afternoon treat or a holiday gathering.

Jump to Recipe

What You’ll Need

Okay, so these cookies are awesome because aside from being fat-free, they use simple ingredients that pack a punch. Here’s what you’ll need:

  • All-purpose flour
  • Whole wheat flour
  • Baking soda
  • Salt
  • Ground ginger
  • Cinnamon
  • Ground cloves
  • Black pepper
  • Fresh ground nutmeg
  • Ground allspice
  • Dark brown sugar
  • Blackstrap molasses
  • Apple sauce
  • Vanilla extract
  • Maple extract
  • Chai concentrate
  • Egg whites
  • Candied ginger
  • Granulated sugar
  • Cinnamon (for rolling)

How to Make Fat Free Gingerbread Cookies

  1. Start by sifting together the all-purpose flour, whole wheat flour, baking soda, salt, and all your spices. You’ll know it’s ready when the spices smell like a warm hug.
  2. In a large mixing bowl, combine the dark brown sugar, blackstrap molasses, apple sauce, vanilla extract, maple extract, and chai concentrate. Use an electric mixer and beat it for about four minutes until everything’s smooth and luscious.
  3. Add the egg whites into your molasses mixture. Beat for another minute until the whites are completely mixed in.
  4. Slowly incorporate your sifted dry ingredients into the wet mixture. Beat until everything is fully combined, creating a rich, aromatic dough. Stir in the candied ginger bits for that extra zing.
  5. Cover the dough and let it chill in the fridge for at least an hour. I personally prefer letting it chill overnight for a deeper flavor.
  6. When you’re ready to bake, preheat your oven to 350°F (175°C). Line a baking sheet with parchment paper or lightly grease it.
  7. Mix the granulated sugar with a dash of cinnamon in a shallow bowl. Scoop a tablespoon of dough, coat it in the cinnamon sugar, and shape it into a ball.
  8. Place each dough ball on the prepared baking sheet, leaving about three inches of space between them. They will spread out as they bake.
  9. Bake the cookies for 10-12 minutes until they’re beautifully puffed and you start to smell that delightful gingerbread aroma.
  10. Once out of the oven, transfer the cookies to a wire rack to cool. Trust me, waiting for them to cool is the hardest part!

Cook’s Notes

Baking these cookies is pretty straightforward, but here are a few tips to ensure they turn out perfect every time. First, don’t skip the chilling step. It helps the flavors meld together and keeps the dough from spreading too much. If you’re planning ahead, you can make the dough and keep it in the fridge for up to two days. Just remember to let it sit at room temperature for a few minutes if it’s too hard to scoop. For leftovers, these cookies stay fresh for about a week if kept in an airtight container. You can also freeze them for longer storage—just thaw before serving.

Make It Your Own

These cookies are versatile, so feel free to experiment with these ideas:

  • Swap the candied ginger for chocolate chips if you’re feeling a chocolate craving coming on.
  • Use pumpkin pie spice instead of the individual spices for a quicker spice mix.
  • Replace the chai concentrate with a strong brewed tea of your choice for a subtle flavor twist.
  • If you want a little crunch, add some finely chopped nuts like pecans or walnuts.

If you try this, I’d love to hear how it turns out—drop a comment or tag me! Baking is all about experimenting and having fun, so don’t be afraid to make these cookies your own. Enjoy every spicy, soft bite!

Related update: Fat Free Gingerbread Cookies

Related update: Triple Citrus Cake

Blueberry, Chocolate & Cocao Superfood Pancakes – Gluten-Free/Paleo/Vegan | Made by Meaghan Moineau

Last Tuesday morning was one of those days where I just needed a little something extra to kickstart the day. You know the ones — when your brain is stuck somewhere between sleep and waking, your mug of coffee is feeling more like a warm hug than a caffeine fix, and breakfast needs to be something special but not overly demanding. That’s when these Blueberry, Chocolate & Cacao Superfood Pancakes came to the rescue. They’re those perfect pancakes that feel like you’re treating yourself to something really indulgent, yet they’re totally guilt-free. Plus, they’re gluten-free, paleo, and vegan! It’s like a breakfast trifecta. Ready to dive in? Trust me, these are worth the short time it takes to whip them up.

Jump to Recipe

What You’ll Need

Here’s the best part: chances are you already have most of these goodies hanging out in your pantry. No need for a special trip to the store when the craving hits!

  • Almond flour
  • Coconut flour
  • Tapioca or arrowroot flour
  • Nut, hemp, or coconut milk
  • Baking powder
  • Vanilla bean paste or extract
  • Himalayan sea salt
  • Frozen blueberries
  • Cacao nibs
  • Dark chocolate

How to Make Blueberry, Chocolate & Cocao Superfood Pancakes – Gluten-Free/Paleo/Vegan

  1. Grab a mixing bowl and combine the almond flour, coconut flour, and tapioca or arrowroot flour with the baking powder and a pinch of Himalayan sea salt. Give it a good mix until everything is nicely blended.
  2. Pour in the nut, hemp, or coconut milk along with the vanilla bean paste or extract, and whisk it all together until you have a smooth, dreamy batter. Let this beauty sit for 10-15 minutes. It’s like letting the batter take a mini-vacation to thicken up.
  3. Heat a smidge of coconut oil in your favorite skillet over medium heat. Once it’s warm and cozy, pour just enough batter into the center to form a pancake.
  4. Cook until the edges start to brown and you see bubbles gracing the surface. This is your cue to sprinkle a few blueberries on the pancake.
  5. Flip the pancake with confidence, cook for another minute or two, then immediately sprinkle cacao nibs and dark chocolate on the top. Let them melt and meld into pure bliss.
  6. Remove the pancake once fully cooked and repeat with the rest of the batter. Stack them up, drizzle with a little agave if you’re feeling it, and savor the moment!

Cook’s Notes

These pancakes are wonderfully adaptable, so don’t stress if you’re missing an ingredient. You can even mix the dry ingredients the night before to save a few precious minutes in the morning rush. Storing leftovers? Just pop them in an airtight container in the fridge, and they’re good for a couple of days. Reheat in a skillet over low heat or simply enjoy them cold. Making a larger batch and freezing them is also an option; just layer parchment paper between each pancake to keep them from sticking together.

Make It Your Own

  • Swap out the frozen blueberries for fresh raspberries or chopped strawberries for a berry twist.
  • Substitute the cacao nibs with crushed pecans or walnuts for a nutty crunch.
  • If you’re not strictly vegan, a spoonful of Greek yogurt with honey makes an unbeatable topping.
  • For a tropical flair, toss in a handful of shredded coconut before flipping.

If you try this, I’d love to hear how it turns out — drop a comment or tag me! Enjoy every delicious bite of these pancakes, knowing you’re starting the day in the best way possible. 😊

Related update: Blueberry, Chocolate & Cocao Superfood Pancakes – Gluten-Free/Paleo/Vegan

Related update: Breakfast Biscuits and Gravy