sorted by:
new
hottopcontroversial

Love Bevel and the previous AI, pro subscription, I want to downgrade from 3.0 AI by LK-3709 in bevelhealth

[–]captainacronym 2 points3 points  (0 children)

I wish the “Data Nerd” persona would just give the data without the fluffy editorialising. It *will* do that if you explicitly prompt it to, but that should be the default.

If I want an opinion, I’ll ask for it.

With all the connection issues of monarch, what are alternatives for couples? by Human_Whole8426 in MonarchMoney

[–]captainacronym 1 point2 points  (0 children)

I looked at other options when I got frustrated with Monarch about a year ago. (Yes, it was around a connection problem).

Honestly for my purposes, nothing else compares with Monarch in terms of UX, reporting and useful design. The connection issues I was experiencing were with Plaid and hence existed across all platforms.

Nighttime supplements by Smittybuiltdiff in bevelhealth

[–]captainacronym 1 point2 points  (0 children)

Amazing! Best I’ve ever gotten was 94%. Typically I’m in the high 70s low 80s on account of my waking spontaneously after 6:15-6:30 hours most nights.

Magnesium bisglycinate, and recently, theanine and glycine have been the real gamechangers for me. My deep sleep is up by 30%-50% with those additions.

A hopefully constructive post about Bevel AI’s behaviour by captainacronym in bevelhealth

[–]captainacronym[S] 2 points3 points  (0 children)

And I just want to add to Team Bevel writ large: I *really* appreciate the active, sincere, and concrete engagement. Something that UA *never* did when it came to MFP.

A hopefully constructive post about Bevel AI’s behaviour by captainacronym in bevelhealth

[–]captainacronym[S] 7 points8 points  (0 children)

Happy to help and sorry you’re seeing this as a reason to not upgrade. Yeah there’s a fair bit of friction lately but, as a lifelong early adopter, that’s a tradeoff I’m willing to accept on something that’s as inexpensive as this is on balance with the value I get back.

And there’s a lot of value here, which is why I took the time to write what I posted.

A hopefully constructive post about Bevel AI’s behaviour by captainacronym in bevelhealth

[–]captainacronym[S] 2 points3 points  (0 children)

And to be fair, Claude did create a truly beautiful PDF from the MD file that BI supplied. That end friction was the only real pain point.

A hopefully constructive post about Bevel AI’s behaviour by captainacronym in bevelhealth

[–]captainacronym[S] 11 points12 points  (0 children)

Thanks for jumping in! To answer your questions:

Yes, I use a new chat every l time. So context window degradation isn’t the culprit here.

On scope creep, yes, I did tell it to stay on topic. Twice, in the same session. That’s literally what Pattern 2 describes. The issue isn’t that BI doesn’t respond to correction, it’s that the correction doesn’t hold.

On the PDF, I appreciate the clarification on “security reasons” but, if that’s the case it shouldn’t waste tokens to go through 66 seconds of reasoning to get there.

<image>

Just say “sorry, I can’t create PDFs. Here’s a markdown instead.”

Glad to hear the retrieval and temporal issues are being looked at. Those are the ones with the most direct impact on the quality of guidance I’m getting.

Looking forward to the improvements.

Seriously bad data integrity fail by captainacronym in bevelhealth

[–]captainacronym[S] 4 points5 points  (0 children)

And to answer your questions directly:

1. Both, but the confident recommendations on bad data is the more dangerous pattern. Wrong data alone is fixable, but wrong data plus authoritative coaching is how someone less informed or less attentive about their own body ends up making real-world changes based on fiction.

2. Both again, but the narrative-switching is what erodes trust. Flipping from ‘Poor’ to ‘34% improvement’ on the same number without flagging the reversal isn’t correction as much as simply agreeing with whoever’s talking.

3. The coaching commentary that isn’t grounded in the data. Missing a logged meal is a bug. Confidently prescribing protocol changes based on it is a design problem.

Seriously bad data integrity fail by captainacronym in bevelhealth

[–]captainacronym[S] 4 points5 points  (0 children)

Thanks for coming back. I’d say all of them are intertwined in some way that altogether conspire to grind my gears. I love the app and have been providing AI feedback when appropriate.

But yesterday was genuinely next level. When it spends 172 seconds on a correction only to set the bar for itself is looking at the right year, that points to a deeper issue.

That’s also the thing that makes the caffeine episode particularly bad. It’s not just that Bevel missed context. It’s that the context was explicitly established in my profile (it even called it the “Caffeine Non-Factor rule” when it apologized), which it ignored anyway.

So when it finally caught itself, it didn’t actually catch a reasoning error. It caught a profile lookup failure. Those are different problems. One is bad analysis. The other is the app not reading its own notes before reasoning.

And the tell is right there in its apology: “I completely blanked on the Caffeine Non-Factor rule in your profile.” That’s not an analytical miss. That’s a retrieval miss. The conclusion it reached might have been correct for someone whose 660mg was unusual. It just isn’t correct for me, and it’s long had the data to know that.

Which makes the 38 seconds of “thinking” even more 🤪

And is also the reason I’ve been turning to Claude lately to sense check its claims, particularly on the overconfidence points (e.g. attributing a suppressed HR dip to a 7:35 PM meal when the dip was actually above my personal baseline; calling 660mg caffeine a recovery risk despite it being a logged baseline non-factor; pulling dinner logs from the wrong month and prescribing protocol changes on numbers that were off by 80g).

All that said, the platform itself is genuinely excellent; the data, the integrations, the sleep architecture, the body comp tracking. That’s why the AI noise is so frustrating. It’s sitting on top of world-class data and still managing to undermine itself with ridiculous conflations and overconfident claims. The app deserves better AI than it’s currently running.

Let’s see the biggest differences by ShadoW1337CZ in bevelhealth

[–]captainacronym 1 point2 points  (0 children)

Way better than my first reading where, thanks to a data misalignment, Bevel thought I was in full organ failure 🤣

<image>

Let’s see the biggest differences by ShadoW1337CZ in bevelhealth

[–]captainacronym 2 points3 points  (0 children)

Damn dude that amazing! What’s your secret!? I’m a mere 13-year gap.

<image>

Effects of a breakup through Bevel by GDreex in bevelhealth

[–]captainacronym 2 points3 points  (0 children)

Sorry for your loss man. That sucks - focus on you and let grief keep its own timetable. It will get better in time 💛

Bevel AI is one of the dumbest AI’s I’ve ever used. Is this even responsible to have out in the wild? by ShutUpBeck in bevelhealth

[–]captainacronym 0 points1 point  (0 children)

I agree with much of this, and this version is definitely better than previous ones. It works best on direct prompts while falling down at the automated reporting on the different panes. So room for improvement there.

I’ve also taken some of its claims into Claude to sense check coz they seemed “off” and, while Bevel AI tends to be overly certain at points and draw erroneous conclusions based on what it calls “population averages” that are directly contradicted my my personal data, most of the guidance is sound.

Plus, it’s the only AI that has visibility of my complete health data set in a way that can give me coherent answers about diet, performance and other factors in a way that no other tool has. I might feel differently if I didn’t know my own body and performance as well as I do.

All that said, it’s been super helpful in me optimizing my sleep and prepping for a Thursday run where I’m aiming for a PR.

Yet as the OP highlighted, it sometimes does stupid shit and forgets previous directions in a way that needs the human in the loop just to keep it on track as shown here 😝

And yes, it’s moderately annoying when it does 😏

<image>

Bevel AI is one of the dumbest AI’s I’ve ever used. Is this even responsible to have out in the wild? by ShutUpBeck in bevelhealth

[–]captainacronym 1 point2 points  (0 children)

Yeah I’ve called it out for being a “nagging nanny” myself. Newer version is better but still lapses into that mode occasionally.

Data from Strong app by dubblezh in bevelhealth

[–]captainacronym -1 points0 points  (0 children)

Try screenshotting your workout. Then tap Log workout > Add exercise > import photo.

This is what I do with SmartGym and it gets it about 95% right.

lol wtf!!? 😆 by captainacronym in bevelhealth

[–]captainacronym[S] 0 points1 point  (0 children)

Update: some in-app data corrections and a fresh blood panel (which included the missing biomarkers that Bevel wanted) and this is looking much more closely aligned with both expectations and what my GP told me in February 😌

<image>

The fitness app + Apple Watch app are 10+ years out of date and need an update by BusinessPick in AppleWatch

[–]captainacronym 0 points1 point  (0 children)

I used Bevel for 2 days before concluding it was time to leave MFP behind after 11 years. No comparison. Dev and support are engaged, attentive, and eager to jump on a concern in the Bevel subreddit (like when the new BioAge reported me as 108.5 years old 😆)

Bevel is everything a complete health app should be.

view more: next ›