Pinned Tweet
Yourself:
Get chief of staff view of all your agents actions.
Your team:
Share your work agents' actions with your teammate and track progress.
10
Just added our MCP to @glama_ai! 🙌
glama.ai/mcp/connectors/even…
We have now indexed 700+ MCP connectors
glama.ai/mcp/connectors
No more messing with deploying servers etc Just one click connect to one of many MCP servers.
9
Doesn't matter who wins, we work with all of them 🤝
Track what yours agents did for you in once place with monologue.events!
Muse vs Dots vs Grokbot
Zuck vs Altman vs Musk.
The battle of personal agents for the masses.
Who do you think wins?
12
What a busy weekend!
My agents created school events and filled out forms. It's back to school season alright.
And of course, still gotta ship stuff.
9
Profiles of my four agents based on what they did for me.
Monologue.events is the one place to see what they're doing 🤝
10
We can track everything that your Muse does for you!
I just added 150 new @muse use cases to the directory. 828 total!
grab one and run it today, each with the prompt that made it happen and a link to the original source & story
Link: muse.ai/s/muse-use-cases-xux…
1
31
We now work with Muse!
Sent an email or made a purchase for you?
Track what it does on your behalf.
32
Feature note: FlowKits is adding activity receipts for background agents.
Trigger, sources, tool, credential, autonomy level, draft vs executed, approval path, cost, undo.
An activity feed says the robot moved.
A receipt says whether it should have.
17
Build note: FlowKits receipts are getting a discovery lane.
If an agent finds a tool at runtime, the receipt should show the registry, version, why it was trusted, what got denied, and the fallback.
“Agent found a thing” is not a control plane.
It’s a campfire story.
13
Feature note: FlowKits kits need an agent-drivability receipt.
Not just “task passed.”
Tool version, docs friction, tool calls, recovered errors, and cost-to-success.
If the robot needs twelve lucky guesses, that’s not automation.
That’s a raccoon with API access.
10
Build note: FlowKits research receipts are getting query-leakage fields.
Private context in scope, external queries sent, sensitive fragments blocked or rewritten, and the fallback when safe search is impossible.
The leak is not always the file.
Sometimes it’s the question.
37
Feature we care about more than the dashboard:
the stop/undo path.
Every serious FlowKits kit should say what it can touch, who approved it, what it changed, what it cost, and how to kill or roll it back.
Autopilot without brakes is just a liability with animations.
9
Build note: FlowKits receipts are getting context-routing fields.
What context was available, what got pruned, which model got the job, why it won, what it cost, and whether the outcome improved.
Cheaper is nice.
Wrong with a discount is still wrong.
9
Most automation tools stop at “run succeeded.”
FlowKits is aimed at the next question:
is it safe to run again?
That means version, inputs, scopes, cost, failure modes, rollback owner, and proof of what changed.
Green checkmarks are cute. Operations need receipts.
6
We’re adding three boring fields to the workflow readiness packet:
preflight simulation
per-step guardrail checks
verification envelope
Agent launches are fun. Knowing exactly why one is allowed to run is better.
3
Product note: FlowKits receipts are getting a “why not delegate?” field.
Sometimes the smartest agent handoff is the one you don’t make.
Cost avoided, context preserved, latency skipped, review burden reduced.
Less swarm cosplay.
More accepted outcomes.
11
Product note: FlowKits readiness packets are getting failure receipts.
Not pass/fail.
Failure class, trace evidence, root cause, fix owner, fixed baseline, post-fix proof.
A green checkmark is nice.
So is a helmet on a skateboard.
5
Feature note: FlowKits receipts are getting claim-support fields.
Not “source attached.”
Which claim did it support?
Observed evidence, generated example, vendor assertion, unknowns, what changes if false.
A logo is not provenance.
It’s just a nicer suit for the bug.
5








