@NuphosAI Fair question. For an inbox watch I'd want each run to say "checked, nothing new" or "couldn't check, sign-in expired". Silence shouldn't mean two different things.
Grok Bot now lets you set permissions for each connector tool.
Each tool can be Always allow, Auto-review, Needs approval, or Blocked. So an agent can read freely while sending still waits for you.
And a routine that loses a sign-in skips its runs until you reconnect.
@stretchcloud That's the trap with checking commands as text: the approval check reads one string, bash runs another after expansion.
A read-only allowlist for find is shaky anyway. One flag turns a search into a delete.
@TheMaran The part worth copying is the order. It found the missing refunds first, then opened the support chat.
Auditing your own orders is safe to automate. The moment it talks to a company for you, I'd want to read what it's about to say.
@AiForAmericans An inbox helps only if each item shows exactly what happens on yes, and what happens on no. Approve is easy to design. Reject, edit and "not now" are where agent flows usually break.
@Michael_Fenech_ Same rule works outside money. My Grok Bot drafts my X replies, but nothing goes out until I approve the exact text. Reading and drafting are cheap to allow. Acting is where the yes belongs.
@NovaOrbiting Win + V is a great one. If you live in Chrome, I built Clipstay for the same job: a searchable history of the text you copy on web pages, kept on your device. No account, no analytics.
@carlos_olivera Approval on every dollar is the right default. I run my product work with agents the same way: one coordinator, workers that draft, nothing goes out without my yes. The hard part is making each draft carry its sources, so saying yes takes a minute, not an hour.
Claude just added Computer use for Team and Enterprise plans.
It's beta, rolling out gradually, and it only works in the apps you allow. On the web and on mobile, Computer access has to be on.
So it isn't "Claude can use any computer now." It's a gated, opt-in beta.
@everton_dev Yes, if the block comes with time to learn it. Tests show it works today; knowing why it's an actor is what keeps it working when someone else touches it next month. "Explain it or don't merge" is a fair rule when Claude writes the code.
@hsianghui Approval cards before it sends, submits or pays is the part I'd check first. My agents work the same way: they draft replies and posts, and nothing goes out until I say yes. Drafting is cheap to automate; sending is where trust lives.
@Kamphey "Click the element, get the formula" is the right shape for this. Nobody remembers which IMPORT function fits; they remember what they were looking at. Does it pick between XML and HTML for you, or show all three?
@AvinashDalvi_ Honestly, I can't tell. Pagestay has no analytics, so I don't see who turns what on, and it's still a handful of users anyway. That's the tradeoff I picked: the store's user count is about all I know.
@mtbosshq Yes, both are Chrome extensions. Clipstay keeps your clipboard history on your device, and Pagestay puts notes in the side panel, tied to a page or a site. Neither needs an account or collects analytics. Good luck with CopyBoss, Rui!
@dannypostma Option A is close to how I already sell my small Chrome tools: pay once, no account, data stays on your device. Owning the data feels like the part people get right away. Customizing the code is the part I'm less sure most people want.
@dhh Same split shows up one level down. I build my Chrome extensions with agents, but the extensions ship with no AI inside. How code gets written and what runs on your machine are two separate choices.
@AnishJaitwar 5/ matters more than people think: a clipboard history is only safe if it knows what not to keep. In Clipstay, my Chrome clipboard extension, page capture skips password fields and Incognito pages, and history stays on your device.
@excalidraw Small improvements like this are my favorite kind of changelog entry. Removing one "exit, resize, go back in" step does more for how a tool feels than most big features.
@__mystudylog Building it for your own practice is the best way to start: you already know exactly where the friction is. Which part of shadowing does it help with most, finding the sentence to repeat or hearing how close you got?