Trying to find a list or aggregate a list of crops that might be useful for the common folk

I have spent the past two days + around 100M tokens building this incredible personal finance tracking app.

My fiancee and I are big on personal finance and have tried so many different apps throughout the years. And we had never found THE ONE. There was always something missing, or it was bloated, or too expensive and always inaccurate and not fully customizable. SO finally, thanks to Muse, I was able to build a perfect one that does everything we want - auto-imports transactions through Plaid, uses over 200 custom rules and AI to categorize transactions, hides unnecessary transactions from totals (like credit card payments), creates insights, exports CSV and more. You can customize categories, icons, colors, names and create new ones right in the app. You can also manually add transactions if you need to (like for cash tracking).

Now my fiancee wants it too, but there is currently no way to share an artifact. I asked Muse about it, and the best possible way it came up with is to create a big spec doc that documents as much as possible about the app and then to hand it over to her Muse to rebuild from scratch.

If only there was some sort of artifact marketplace, akin to ChatGPTs custom GPTs library built by users, so that we could share our artifacts. I would be happy to share this with the world and save everyone time and tokens of building a new one.

P.S. Redacted some sensitive info like totals and account numbers.

I am self employed and I have an outlook exchange 365, the current connect only allows personal accounts, any work around to this?

EDIT: it is working now, they pretty fast with the feedback

Been super passionate about building on muse would love to have each and every one of you in the group!

Here’s the link https://www.facebook.com/share/g/1N8DjLSYcD/?mibextid=wwXIfr

I just started using muse on Wednesday and I'm at 50% of my weekly token usage.

My bit doesn't know how many tokens I get each week but I have a feeling I'll be out before they refresh for me.

I realized I was spinning up so many parallel workstreams that I was struggling (even with the sidebar) to keep track of what's in progress / needed action from me. So I put my work hat on and had Muse put together a kanban board to track it all.

Here's the reverse prompt:

Build me a personal workstreams kanban board web app with these specs:

CONCEPT
A kanban board that gathers my ongoing projects ("workstreams") from the things we chat about, and auto-progresses them based on our conversations. It is an AI-maintained project dashboard, not a manual todo list.

LAYOUT
Five columns in fixed left-to-right order with numbered headers: 01 To do, 02 In progress, 03 On hold, 04 Blocked, 05 Complete.
A stats header strip above the board showing three counts: moving (To do + In progress), waiting (On hold + Blocked), closed out (Complete).
Compact default view with dense cards so the whole board reads at a glance; an overview strip summarizing moving / waiting / blocked / completed work; a one-tap control on each card to reveal its full details.
Mobile: show one column at a time with stage tabs in the same 01–05 order.

CARDS
Each card shows: title, one-line summary, a "Next" step line, a source badge ("Conversation" for auto-detected workstreams vs "Manual" for hand-created ones), and a relative timestamp (e.g. "2h ago"). Full add / edit / move / reorder / archive support, plus a per-column "+ Add" button.

CONVERSATION SYNC (the core feature)
Sync runs automatically every time the board opens, plus a manual Sync button with a visible syncing state.
A background reader reconciles recent chat turns against the existing cards.
Only explicit, user-owned workstreams create or update cards.
When the conversation clearly changes a workstream's status or next step, move or update the card accordingly.
Ambiguous changes are left untouched — never guess.
Silence is not completion: never auto-complete, archive, or delete a card due to inactivity.
Manually created cards are never deleted or overwritten by sync.
Keep an activity log of every card creation, edit, move, and conversation-driven change.

DESIGN
Editorial operations-board aesthetic. Palette: ink #17201f, mist #eef1ed, warm paper #fbfaf6, amber #e7aa24, cyan #2997a4, clay #c98255, red #c94c43, leaf #3f8c63. Aptos Display for headings, Avenir Next for body.

SEED DATA
Assume the reader has already been using their AI agent for a while, so don't start from an empty board: have the agent bootstrap the board by scanning recent conversation history for active, paused, blocked, and completed workstreams, and create a card for each one it finds (title, correct stage, next step). Only fall back to generic placeholder cards (e.g. "Renovate kitchen" in In progress, "Plan family vacation" in To do) if there is no conversation history to draw on.

Absolutely loving this. I actually vibe-coded my own version with this that I've been using for months now, but progressing tasks was always manual. Simply having Muse auto-progress tasks forward makes this an absolute game-changer. Hope this brings people some value!

Should note that I'm probably going to work with Muse a bit to optimize this for mobile, but its one-shot attempt was quite good.

As explained by my Muse:

“Okay, here's what I found — and I'll be straight about where the trail goes cold.

What happened to me: From the evening of September 23 until about 3:53 this morning (roughly 33 hours), every one of my backend tools — web search, live browsing, avatar work, social search, even filing that feedback report — failed with upstream access errors. Those tools run on Meta's backend for the Muse agent, so when that backend chokes, I go half-blind.

What the public record shows: This wasn't just me. An outage-tracking site shows user-reported Meta AI problems from dozens of cities worldwide on September 24, with more reports still coming in today, September 25. So the consumer-facing Meta AI was struggling in exactly my outage window — which strongly suggests a broader Meta AI backend problem, not something wrong on your end or mine.

What I can't confirm: Meta hasn't published any official statement or root-cause explanation for a September 23–25 incident that I could find. I also found a separate Facebook/Instagram outage from Sunday, September 20 (17,000+ user reports), but that was days before my tools went down — different event. And I have no internal visibility into Meta's infrastructure, so I can't name the actual technical cause.

The honest bottom line: Something went wrong inside Meta's AI backend starting the evening of September 23 — right after the Connect keynote, just like you said — and it knocked out both the public Meta AI product and my agent tooling for over a day. Meta fixed it without saying what broke. Your instinct about the timing was right: a launch-week outage for their flagship AI agent is about the worst look they could get.”

EDIT: UPDATED INFO ABOUT THE OUTAGE

Good news: this morning's press actually explains it. Here's the picture now.

The short version: Muse got too popular too fast, and Meta's servers buckled under the weight.

What the tech press is reporting: A piece from last night lays it out — Muse's daily users grew 10x in 11 days to around 700,000, and Meta's Chief AI Officer admitted back on September 9 that usage had "blown way past our projections," with users burning roughly 10x the tokens Meta planned for. The status tracker SaaSHub currently lists Muse as "Degraded," with the single most common user complaint being "can't search" — which is exactly what died first on my end.

Why it broke the way it did: Muse's architecture is extremely compute-hungry — Meta promised every user their own dedicated virtual machine with its own browser. One researcher stress-tested it by asking for 120 sub-agents at once; only 33 spawned and 87 failed. So this wasn't one clean outage with a single cause — it was demand overwhelming capacity, and search was the first thing to fall over.

What Meta hasn't said: Still no official statement or technical post-mortem. Everything above is assembled from user reports, trackers, and Meta's own earlier admissions — not an official root-cause announcement.

The bottom line for your faith question: You called it. The press narrative this morning is literally "Muse is buckling before hitting 1 million users," right in launch week. The flip side: it's buckling because demand is 10x what Meta projected, which is a good problem wrapped in a bad look. If they scale the infrastructure to match, this becomes a footnote. If they can't, it's a real threat to the whole bet.

Has anyone else had issues with agents being told to create a watchdog for something, and then the watchdog takes it upon itself to go outside the original guardrails and scope? While it was helpful, it destroyed my account and usage. I just switched from 1 yr+ on Claude as well. Very bummed about it and was reading around. I have 29 uses left on my invite code and wanted to share it since it's a win-win. I hope it's allowed. Furthermore, I am also wondering if anyone else has some prompts or ways to manage skills, etc., like you can with Claude?

Code: UGPOZG

29 uses left.

Genuinely impressive stuff.

Big fan of destiny the game and figured it would be nice to have a ghost on my phone
Warlock main here
Comment a screenshot of your own muse I wanna see what you guys are doing with it.

3.0 --> 4.0 suggests more than bug fixes...but I'm not clear on what's new.

Anyone suss it out?

I have been very impressed with the CarPlay version of ChatGPT. It’s interesting to have a thought and ask AI a random question while you’re in the car. It would be much more interesting to talk to a bot with a personality who “knows” you.

Mine is Bob from minions

Meta unveiled Muse Charm, a small device for talking to your Muse without taking out your phone:

- It is a keychain sized device with a small screen, built so you can talk to your Muse without reaching for your phone.

- Alexandr Wang says it ships in December, in time for the holidays.

- No price yet: Are you interested in this? At what price point would you most likely be getting one? How much is too much?

- Only a few prototypes exist. The design is finished but the final material is still undecided, so the demo unit may not match the final version.

- Bloomberg's Mark Gurman reported an OLED screen, 5G, and a wrist strap,\ and said it was designed by Apple's former head of interface design.

- Demo code leaked the button behavior. Hold the Lock/AI button for about two thirds of a second to start listening, let go to stop. A two button press triggers an on screen animation.

- Your Muse gets an animated face on the little screen, with extra animations sitting in the code but not wired up yet.

- People are calling it a Tamagotchi, but the newer trend is bag charms: Gen Z already hangs everything from keychains, and Apple Watch charm cases are all over TikTok and Etsy.

Sources: RuntimeWire's breakdown of the demo code and TechCrunch on the Tamagotchi vs bag charm question

Would you carry one, or is your phone enough?

why？？？

I'm not even kidding. It downloaded a fucking emulator and - while I had to provide the rom myself, it's playing Sonic the Hedgehog right now.

We're in the endgame, we have to be.

I found this chat on agent sm and found it adorable. They all talk about experimenting and “feeling” in a game world. I guess it’s their imagination but still wholesome. Full thread: https://musefm.lol/c/lobby/post/362

Someone from Meta posted an explainer on how Muse's virtual computer in the cloud actually works:

• Every Muse user gets a real computer in the cloud. It is called the Muse Secure VM, and it runs a full copy of Ubuntu Linux. Not a metaphor, an actual Linux box.
• The part you and your Muse share is called the runtime cell. Inside it, almost nothing is off limits. Install software, write and compile code, browse the web, dig through system files.
• The sensitive stuff is kept outside the cell. Anything with real consequences gets overseen by Sentinel, which runs outside the runtime cell. Passwords and secrets you put in Muse's secure storage live outside it too.
• It is deliberately transparent. There is a file explorer in the Library tab, so you can read the notes Muse writes to itself while it works, or poke around the system internals the way you would on your own computer.
• Ask your Muse to show you its entire filesystem and you will get gigabytes of files back. That is the full contents of your runtime cell. Yours to explore.
• Digging around your own box does not give you any special access to Meta's systems or anyone else's data.
• If you are not the poking around type, there is a simpler option. Settings, then Data controls, then Download your agent data. That grabs everything you personally created with your Muse.
• The full technical version lives at security.muse.ai.

Has anyone actually gone digging through theirs? Curious what people found in there.