Field Notes - Tygart Media

Category: Field Notes

  • Do Not Ask the Bot to Do Everything

    Do Not Ask the Bot to Do Everything

    Inspired by Texas Twins Dad: if Grok Bot usage makes you nervous, do not ask it to do everything. Ask it to brief the work. Route coding to Cursor Cloud or GitHub. The Bot stays in the middle — goal, clear handoff, review the PR, next ask. Less spinning. More shipping.

    That is the same desk we already run. Voice writes the ticket. Cursor does the hands. The Bot is not the van. The Bot is the clipboard between the walk and the shop.

    “Do everything” is how a shift turns into a rumor. The model tries to own the goal, the code, the merge, and the receipt. Then you wake up to a PR you cannot refuse because you never wrote the ticket. Briefing is the opposite. Name the goal. Name the handoff. Name who reviews. Leave the next ask blank until the receipt exists.

    Nervous is useful. Nervous means you still want a human on Send. Keep the Bot in the middle of the pipe, not at both ends. Goal in. Handoff out. Review the PR. Then the next ask.

    If you cannot point to the brief, you did not staff a shift. You asked a teammate to live in every room at once.

  • The 2 A.M. Card

    The 2 A.M. Card

    Inspired by the lock cluster we just wrote — Gilang on passwords, Moritz on scopes, SmartSentinels on bounded approval, BridgeMind on rollback — and by the shop rules already live: who holds the keys, a key is not permission, bounded approval is the hire.

    One card. Five lines. Fill it before the Bot gets a connector.

    • Allowlist. Which tools. Not “Gmail.” Draft only. Not “WordPress.” Draft only. Not “Cursor.” Open a PR. Name the verb.
    • Cap. How much. Words, dollars, deploys, sends. A number you can say out loud at 2 a.m.
    • Expiry. When the badge dies. Dawn is a good default. Infinite is not a shift. It is a leak.
    • Undo. How you roll the night back without taking the shop down. Revert, unsend, revoke token. Write the path while you are awake.
    • Who pulls the plug. One name. Not a channel. Not “us.” The person who can kill the badge without asking a group chat.

    If a line is blank, you did not hire a teammate. You left the keys on the seat and called the empty van a desk.

  • Bounded Approval Is the Hire

    Bounded Approval Is the Hire

    Inspired by SmartSentinels — bounded approval is the difference between hiring an agent and handing it the keys — and BridgeMind: overnight agents need isolation, scoped permissions, checkpoints, and a rollback path.

    That is the shop rule written as a contract. A key is not permission. Permission without a cap is still a gift of the van. The hire is the bound: which tools, how much, until when, and how you undo the night if the receipt is wrong.

    We already staff shifts. Voice writes the ticket. The Bot runs if a connector exists. The human keeps Send. Bounded approval is that stack named out loud. Allowlist the tools. Cap the spend. Set an expiry so the badge dies at dawn. Keep a rollback so a bad merge is a revert, not a rumor.

    Unrestricted overnight access feels like trust. It is the opposite. Trust is a small door you can close at 2 a.m. without taking the whole shop down with it.

    If you cannot name the allowlist, the cap, the expiry, and the undo, you did not hire anyone. You left the keys on the seat and called the empty van a teammate.

  • A Key Is Not Permission

    A Key Is Not Permission

    Inspired by Moritz Kaminski: an API key answers whether a request is authenticated. It does not answer whether an agent should take a specific action or spend a specific amount. What belongs next: tool scopes, approval rules, spend limits, and an audit trail.

    That is the same sentence as last night, said from the other side of the lock. Who holds the keys is ownership. What the key is allowed to do is the job. Mixing those two is how a shop hands a Bot the van and calls it a teammate.

    A signed request is not a signed job. Gmail connected is not send. WordPress connected is not publish. Cursor open is not merge. The badge gets you in the door. The desk still writes the ticket: which tool, which action, how much, done-when, and who can pull the plug at 2 a.m.

    This is why the email rule is not manners. Resolve the person. Show the draft. Wait for the yes. Log the near-miss. The connector fetches. The human authorizes. Same shape as a spend cap: the Bot can draft against a live inbox and still not touch Send.

    If you cannot name the scope, the cap, the yes, and the receipt, you did not hire an agent. You left a signed key on the table and hoped the night would be kind.

  • The Next Lock Is Who Holds the Keys

    The Next Lock Is Who Holds the Keys

    Inspired by Gilang: Astra can run the computer, a Grok Bot can log into tools overnight, Tesla took the driver out of the car. Everyone celebrates teammates. Nobody asks who still holds the passwords. And by 0xTangent: capability demos are cheap. Who can revoke the agent at 2 a.m. is the product question.

    That is the sentence the shop already lives on. We wire connectors so the Bot stops spinning. We write the ticket so Cursor has hands. We still do not hand over the keys.

    A teammate with your Gmail is not a Chief of Staff. A teammate with your WordPress app password is not a publisher. A teammate with the van keys is not the owner. The model can book, draft, and drive. The irreversible step still needs a name you can fire.

    This is why the one-writer rule exists. Four agents can research. One seat writes. This is why the email rule exists. Resolve the person. Show the draft. Wait for the yes. The connector fetches. The human signs.

    The next monopoly is not the cleverest overnight fleet. It is the desk that can revoke a badge in one move and still have a receipt of what the badge did. If you cannot answer who pulls the plug at 2 a.m., you did not hire a teammate. You rented a hole.

    Staff the shift. Keep the keys. That is the adult product.

  • Chat Is a Room. Overnight Is a Shift.

    Chat Is a Room. Overnight Is a Shift.

    Inspired by Kimi Nguyen asking which you would rather have: Astra in the chat, or a Grok Bot doing the work overnight.

    That is not a product question. That is a shift question. A chat is a room. You walk in, you talk, you leave. An overnight Bot is a shift. You write the ticket, you go to bed, you read the receipt in the morning.

    We already said it twice this week. Voice writes the ticket. Cursor does the hands. And the overnight nudge is not a teammate until it leaves a receipt you can refuse. Same split, different names. Astra in the thread is last-mile talk. The Bot on a connector is a scheduled pair of hands — if you scoped the hands before you paid the bill.

    People lose money here because they buy the room and expect the shift. They leave a chat open and call it a teammate. Then they are surprised when nothing moved while they slept. The model did what a room does. It waited for the next sentence.

    The shop rule is blunt. If you need a conversation, sit in the room. If you need work to exist at 6 a.m., write the ticket, name the connector, name the done-when, and let the shift run. Do not ask a room to cover a night. Do not ask a night shift to replace the room.

    Kimi asked which you would rather have. The honest answer is both, in different hours. Buy the room for the walk. Staff the shift for the sleep. The mix-up is what turns a good tool into a rumor.

  • You Can Email People. That Is Not a Desk.

    You Can Email People. That Is Not a Desk.

    Inspired by Melvin Hagberg — “you can literally just email people” — and Joe Benson riffing that the reply came from a Grok Bot Chief of Staff on the Gmail connector.

    The joke lands because both halves are true. You can email people. A stranger with a short note still gets further than a stranger with a pitch deck. That is not new. What is new is treating the send button like a company.

    A note is a moment. A desk is a pipe. The note leaves your fingers. The desk reads the thread that already exists, drafts against the real inbox, and stops at the human yes. Same Gmail. Different job.

    We already wrote the warning: without a connector the Bot just spins. The inverse is also a trap. Wire Gmail and you still do not have a Chief of Staff. You have a drafter with a badge. If the Bot hits send on a name you did not confirm, that is not leverage. That is a hole in the floor.

    The shop rule is the same as the house rule. Resolve the person. Show the draft. Wait for the yes. Log the near-miss. The connector does the fetch. The human does the irreversible step.

    So yes — email people. Do it more. Do it shorter. Do not confuse that with standing up a teammate. The teammate earns the title when the receipt lands in the Hub and the name on the To: line is the name you meant.

  • Without a Connector the Bot Just Spins

    Without a Connector the Bot Just Spins

    Inspired by Chelm’s Deep on a weekend with Grok Bot: it works when it has a connector. Without one it spins and tries to do things badly. Email and shopping got checked off. That is the whole brief.

    People keep buying a teammate and then starving it. They load skills, routines, instructions, scripts. They forget the one thing that turns talk into a checked box: a live pipe into mail, calendar, the Hub, or Cursor.

    Without that pipe the Bot is a very polite intern with no badge. It drafts. It shops in the abstract. It writes four versions of an email you already meant to send. Motion. No receipt.

    With a connector the job changes. The Bot reads the thread. It drafts against a real inbox. You still hit send. That last tap is the product, not the personality of the model.

    Same split we already run on the desk. Voice Mode can use the connectors and still is not the shop. Voice writes the ticket. Cursor does the hands. The Bot is the overnight teammate only after the ticket names a system it can actually touch.

    Do not confuse a loaded prompt with a loaded shop. A wall of instructions is not a Gmail connector. A skill file is not a calendar. If the Bot is shopping your weekend list with no cart and no card, that is theater. If it is drafting the vendor note in the same thread the vendor already sits in, that is work.

    Wire one connector. Give it one list. Watch what gets checked off. Then add the second pipe. The fleet can wait. The badge cannot.