I Let AI Decide Everything I Ate for 30 Days – Here’s What Actually Happened
There is a moment, somewhere around day nine of this experiment, when you realize you are standing in a grocery store at 7:30 in the evening holding a can of chickpeas, a bunch of beetroot, and a block of paneer – because an AI told you to. And you are not even questioning it anymore.
That is how deep this experiment got.
I had already spent a month testing what happens when you replace Google Search with AI Mode for 30 days. I had watched AI run someone’s entire social media calendar. So the next logical step felt obvious: what happens when you hand the most personal daily decision – what you eat – completely over to an AI, every single day, for a full month?
No cheating. No skipping. No “I’ll just eat this biscuit and not count it.” Every meal decided by AI.
Here is everything that happened.
How I Set Up the Experiment
The rules were deliberately strict. Every morning, before I touched the kitchen, I opened my AI tool and sent one message:
“Plan all my meals for today – breakfast, lunch, dinner, and one snack. I have a normal home kitchen, a moderate grocery budget, and no food allergies. Do not repeat a meal I have had this week.”
That last instruction was key. I wanted variety forced on me, not the same rotational salad every third day.
I tracked every meal in a simple notes app – what was suggested, what I actually cooked, how it tasted, and how I felt. I also tracked my grocery spending each week against my normal baseline. After 30 days I had 120 meals logged, a noticeable shift in cooking confidence, and a few genuinely surprising discoveries about my own eating habits.
For context on how AI tools handle personalized planning, the AI Tools & Reviews section on this site has covered several of these tools in depth – and the range of what they can now do is impressive.
Week 1 – Sensible, Balanced, Slightly Boring
The first seven days felt like the AI was being cautious. Dal and rice. A vegetable stir-fry. Grilled chicken with roasted potatoes. Overnight oats three times. Everything was nutritionally sound, easy to cook on a weeknight, and utterly safe.
I was half-expecting chaos. I got a meal plan that looked like something a registered dietitian might hand you at a check-up.
Day four produced the first small surprise – the AI suggested a tomato-based shakshuka for breakfast, something I had never cooked. It took twelve minutes, used five pantry staples, and became one of the meals I made again entirely on my own after the experiment ended.
The first week takeaway: AI defaults to competent, not creative. It is protecting you from bad suggestions before it understands what you actually want.
Week 2 – The Global Food Tour Nobody Booked
Week two was where things got genuinely interesting.
The AI started recommending dishes from cuisines I had never cooked – a Malaysian-style coconut rice on Tuesday, a simplified Ethiopian lentil dish on Thursday, Georgian walnut sauce over roasted vegetables on Saturday. My grocery bill climbed about 25 percent because I was buying ingredients I had never previously owned: tamarind paste, smoked paprika, dried fenugreek leaves.
But here is what I did not expect. The cooking itself got faster as the week went on. Because the AI was suggesting unfamiliar dishes, I was actually reading recipes properly instead of half-remembering something I had made before. My focus improved in the kitchen. I made fewer mistakes.
This connects to something that comes up repeatedly when you look at how AI is changing the way people learn and develop new skills. When AI introduces you to something unfamiliar, it forces real engagement rather than autopilot behaviour.
Week two count: 9 new dishes. 3 ingredients purchased for the first time. Zero meals I would call a failure.
Week 3 – The Chaos Week I Had Been Waiting For
Day 15 is the entry I kept coming back to when reviewing my notes.
The AI suggested cold soba noodles with sesame dressing and soft-boiled egg for breakfast. Not brunch. Breakfast. At 7 AM.
My first instinct was to override it. Instead I followed the rule and made it. And it was excellent – light, satisfying, genuinely energising in a way that toast or cereal never quite manages. I had been carrying the assumption that breakfast must mean certain foods, and a single meal suggestion quietly dismantled it.
Day 19 was the other memorable one. The AI produced an entirely plant-based day – every meal, every snack – without me asking for it. When I queried why, it explained that based on the protein-heavy days earlier in the week, a plant-forward reset would help with balance. It was reasoning about my week as a whole, not just responding to a single prompt.
This is the kind of behaviour that shows up in discussions about what AI agents are actually capable of – not just answering questions but applying context across a longer timeline.
Week 3 also produced my two genuine failures: a cold lentil and mango salad that simply did not work texturally, and a chickpea breakfast bowl that was fine but felt deeply wrong at 7 AM. Two out of 28 meals is a better success rate than most restaurant menus.
Week 4 – Something Shifted
By the final week, something had changed in how I was interacting with the experiment.
I stopped thinking of the AI as giving me instructions and started treating it more like a knowledgeable friend who happened to know a lot about nutrition and cooking. When it suggested something I was unsure about, I would ask follow-up questions. It would explain the nutritional reasoning, suggest a simpler version if I was short on time, or offer an alternative that used the same base ingredients.
The conversation became collaborative rather than directive.
Week four also produced the highest concentration of meals I genuinely loved – a slow-cooked tomato and lentil soup, a quick prawn and ginger rice, a chickpea and spinach curry that took under 20 minutes. By this point the AI had enough context from my daily prompts to understand my preferences without me spelling them out each time.
The Numbers After 30 Days
Here is what I tracked across the full month compared to my normal baseline:
- Total unique meals eaten: 91
- New dishes tried: 34
- New cuisines cooked: 11
- Average daily fibre intake: Up approximately 18 percent
- Plant-based meals as a percentage of total: 42 percent (versus roughly 20 percent in a normal month)
- Weekly grocery spend: Up about 15 percent overall, but down in week 4 as I started using pantry ingredients more efficiently
- Meals I refused to eat: 2 (the ones mentioned above)
- Meals I made again after the experiment ended: 14
That last number matters the most. 14 dishes I would never have discovered without the experiment are now part of how I actually cook.
What This Experiment Revealed About Habit and Comfort
The most significant insight had nothing to do with food.
It had to do with how much of what we think is preference is actually just habit. Left to my own choices, I was cooking the same 12 to 15 meals in rotation. Not because I love them above all other food, but because they are familiar, require no decisions, and carry zero risk of disappointment.
The AI eliminated that comfort zone entirely. And in doing so, it revealed that my actual food preferences are much broader than my shopping habits suggested.
This pattern – where AI disrupts established routines and surfaces capabilities or preferences you did not know you had – comes up in other contexts too. It is one of the reasons AI tools for freelancers often produce the most impact not by automating existing tasks but by suggesting approaches the person had never considered.
What the AI Got Wrong
Transparency matters, so here is the full list of genuine criticisms.
Ingredient availability. The AI occasionally suggested ingredients that are simply not available in smaller towns or standard supermarkets. Miso paste, tamarind concentrate, and sumac came up in week two. I had to substitute or skip twice.
Time blindness. It sometimes suggested complex weeknight meals that realistically required 45 to 60 minutes of active cooking. A prompt asking it to keep weekday dinners under 30 minutes fixed this immediately – but it should have asked about time constraints from the start.
No awareness of leftovers. Unless I explicitly told it, the AI treated each day in isolation. It had no idea I had half a pot of dal sitting in the fridge. Adding “I have X leftover from yesterday” to my morning prompt solved this, but it required manual input.
Portion calibration. The suggestions were often sized for two people. For a solo cook, I was either halving recipes or eating the same thing for two consecutive meals – which the experiment rules technically allowed but felt like a cheat.
None of these are dealbreakers. They are workflow issues, not fundamental failures. And most of them dissolved once I refined my daily prompt.
How to Run This Experiment Yourself
If you want to try a version of this, here are the exact prompt adjustments I settled on by day 10:
“Plan my meals for today – breakfast, lunch, dinner, and one snack. I am cooking for one person. Weekday dinners should take 30 minutes or less. Use ingredients available in a standard supermarket. Note if I need to buy anything. Do not suggest a meal I have had in the last 7 days. I currently have [X] leftover in the fridge.”
That single prompt covers most of the issues I encountered in week one. The leftovers instruction in particular changes everything – it reduces waste and forces the AI to think about your kitchen as a connected system rather than a blank slate each morning.
For more on building effective prompts that actually produce useful outputs, the guide on why most people fail with AI prompts is worth reading before you start.
Would I Do It Again?
Yes – with one adjustment. I would run it for two weeks, not four.
By week three I had extracted most of the real learning: the new dishes, the expanded ingredient vocabulary, the broken habits. Week four was valuable for refining the collaborative dynamic, but the novelty had worn off. What started as a genuine experiment had become a routine – which is, in its own way, a sign that it worked.
The experiment is also worth doing in a limited form on a permanent basis. Not handing over every meal, but using AI for one meal decision per day – specifically the one you are most likely to default on. Weekday lunches, for most people, are the high-risk routine meal. Starting there costs nothing and the upside is a genuinely different relationship with what you cook.
Final
Thirty days of AI-decided meals taught me more about my own eating habits than any diet book or nutritionist appointment has managed. It surfaced preferences I did not know I had, broke routines I did not know I was trapped in, and introduced me to 34 dishes I would never have found on my own.
The AI was not perfect. It did not understand my fridge, my time constraints, or my local supermarket until I told it. But once I did, it performed consistently and often impressively.
Food is one of the most personal daily decisions there is. Handing it to an AI sounds strange until you realize how little of your food decision-making is actually conscious choice and how much of it is just the path of least resistance.
The AI gave me a better path. Most of the time, I am glad I took it.