Entries matching “check-in”

Amir Nurani

@amirnurani

4:15am. Meta Muse just checked me into my flight. AI went from answers to actually running the day. Stay curious.

Zack Gabbard

@zac70182

@Muse is fantastic! Very impressed. @finkd After importing memory, I asked it to build a personal trainer and it went full systems-engineer on it. It First asked me a series of questions related to my health, gym access, limitations etc. Then it built a program based off of my

Eric Fitzpatrick

@FITZPAE

Muse became my personal dietitian after I found that I had high blood sugar last week; really cool to have someone check in and help me plan + monitor each day!

I've been running my work in Codex as project folders, and recently tried to properly understand how Muse Goals work under the hood. Made it a goal — good way to watch the machinery operate on itself. The structural problem is worth naming: the current design is a halfway house between two coherent designs, and it gets the costs of both. Design A is Codex: the project is a container. Everything — chat, state, artifacts, scheduled work — lives in one place. My course project has one tracker file, explicit resume rules for new chats, and the curriculum never holds status. Legible, but you have to go to it. Design B is full ambient: no containers at all. The goal is just context that wakes up wherever you mention it, and there's no Goals tab pretending otherwise. Muse picked ambient for activation — talk about the goal anywhere, it wakes up, you never "open" it. But then it built half of containment: a Goals tab showing summary, artifacts, activity, without the other half. Conversations, check-ins, and briefings still leak into whatever chat they happened in. So you get the scattering of ambient with the implied promise of a container. That's the worst combination. The fix is to