The thread is the work product. The phone and the desk are two places you hold it. Sharing is how a human who is not in Grok gets the result.
Why this matters
People do good work in a truck and then cannot find it at the shop computer. Or they screenshot fourteen bubbles and drop them in a group text. The first is a sync problem. The second is a courtesy problem. Both waste the job.
If you signed into the same account in A1 and A4, the conversation you started on the phone should appear on grok.com, and the other way around. Sync is usually fast and sometimes not. You need a method that survives a delay.
You also need a handoff. Colleagues, clients, and family should not have to stand inside your Grok account to use what you made. Ask Grok for a note that can travel: plain text, a short brief, a list. A gallery of screenshots is not a method.
Teach
Same account, two surfaces. Before you chase a missing thread, confirm the email or login on the phone matches grok.com. Two accounts is the most common “sync is broken” story. It is not broken. You are looking in the other house.
Start where the facts are; finish where the keyboard is. The usual loop:
- Phone: voice, camera, a rough field note (you did this last lesson).
- Desk: open the same thread on grok.com. Read it. Add the constraint you forgot. Attach a file if the desk has it. Fast or Think as the job requires.
- Handoff: ask Grok for a 12-line note a person can use without the thread.
- Send that note through the channel the person already uses — email, text, radio board — not a tour of your chat history.
The reverse loop is also good: start the brief on grok.com, pick it up on the lot, add what the camera sees, send the handoff from the phone.
Name the thread so both surfaces show a title you recognize. If the app uses the first line as a title, make that first line the job.
When sync lags. Do not start a second thread “just for now” unless you must. If you must, copy the last usable block — field note, facts, constraints — into the new thread in one paste, and write Continued from phone; treat this as source. Merge later by picking one survivor and deleting the stray. Two living threads on one job will diverge. You will not notice until someone follows the wrong one.
Share the result, not the mess. Grok may offer a share link for a conversation. Use it only if the recipient should see the whole thread, including your half-formed asks. For most work, they should not.
Prefer a handoff prompt:
Write a Handoff Note a coworker can use without this chat.
12 lines or fewer.
Include: what we decided, the facts we trusted, the facts we did not verify, the next action, and who owns it.
No slang about Grok. No "as an AI."
If a fact came only from the camera or only from Search, mark it.
If you need a link for yourself — another device, a bookmark — that is fine. Treat a public or forwarded link as public. Do not share a thread that still has a photo of a panel inside someone’s house, a child’s name, or a client file.
What not to sync. Voice audio does not always become a perfect transcript. Images may be in the thread on one surface and slower on the other. If the desk cannot see the photo yet, say so: “The phone photo is of [object]. The field note is the source until the image lands.” Do not re-guess the label from memory if the note already quoted it.
This pathway is not about posting to X. If you publish, you chose a public surface. That is a different contract than a private desk thread.
Worked example
The tech from the last lesson has a six-line panel note on her phone. At the shop computer she opens grok.com, same account, finds panel field note. The photo is there. She attaches the shop’s one-page reset SOP (a .txt) and asks Fast to merge: field note + SOP, still under 12 lines, no invented amperage.
She then asks for a Handoff Note for the apprentice: what to reset, what was not readable, who to call if the bottom-left breaker trips twice. She pastes that into a text. She does not forward the Grok share link. The link still has her talking to herself about glare and a joke about lunch.
If grok.com had not shown the phone thread after a minute, she would have pasted the six lines into a new desk thread named panel field note — desk copy and proceeded. She would not have re-described the panel from memory.
Your turn
You will touch both the Grok mobile app and grok.com. Use the field-note thread from the last lesson if you still have it. If you do not, do a 3-minute mini version on the phone first (one photo, one six-line note) so there is something to sync.
The artifact has to prove two surfaces and a handoff. Reading this page cannot produce the stamp from Grok or the line you add on the second surface.
Exercise a4-l02-e1
| Field | Value |
|---|
| whereToDo | mobile |
| also | grok.com (same account, same thread) |
| time | 16 min |
Copy-ready prompt (phone)
Step A — phone (Grok app)
Open the field-note thread. Send this (type or say):
PHONE MARKER
Add one fact I can see now that is not already in the field note.
If you cannot see anything new, write "no new visual; waiting at the desk."
Then reply with the single line:
PHONE MARKER: [the new fact or the waiting line] — [today's date]
Leave that thread. Do not copy the whole chat yet.
Copy-ready prompt (desk)
Step B — desk (grok.com)
Sign in. Open the same thread. If it is not there after a short wait, create handoff — desk copy, paste the field note plus the PHONE MARKER line, and continue there.
Send:
You should be able to see a PHONE MARKER in this thread. Quote it exactly.
I am now on grok.com.
Write a Handoff Note for a coworker who will never open Grok:
- 12 lines or fewer
- Decision or job
- Facts we trust (mark camera vs file vs Search vs my words)
- Facts we did not verify
- Next action and who owns it
- No "as an AI," no Grok tutorial
Then write a Sync Receipt:
- Thread title:
- Quoted PHONE MARKER:
- Surfaces I used (phone app + grok.com):
- Share method: handoff note (not a screenshot dump)
- Session stamp: today's date and "Sync receipt written by Grok on grok.com."
Step C — send it somewhere real
Paste the Handoff Note into a message to a real person, or into a note file you will actually use. You do not have to paste their reply here. You do have to tell us where it went (text, email, paper, your own task list).
Artifact to paste
- The quoted PHONE MARKER (Grok must quote it; you must have created it on the phone).
- The Handoff Note.
- The Sync Receipt.
- One line from you:
Sent the handoff to: [channel]. Same account on phone and web: yes/no.
Rubric
- Pass: PHONE MARKER appears, quoted, with a date. Sync Receipt is stamped and names both surfaces. Handoff Note can stand alone (a coworker would know the next action). You state where you sent it. If sync failed, the desk copy still contains the marker and you said so.
- Fail: Desk only, or phone only. A receipt you typed without Grok. Screenshots described as a handoff. Two different jobs mashed together. No PHONE MARKER. You used a second login and called it sync.
Common failure
The common failure is the screenshot stack. It feels like sharing. It is not. The recipient cannot search it, cannot copy a number without errors, and cannot tell which bubble is the decision. If you catch yourself grabbing the third image of a chat, stop and run the Handoff Note prompt.
The other failure is dual accounts. Personal Gmail on the phone, work login on the desk. You will blame Grok. Check the account first, every time the thread is “missing.”
What’s next
A1–A4 is the working kit: a door, a brief, a thread you steer, a desk with tools, a phone that can see. Later beginner modules cover research discipline, Imagine for work, and an everyday operating system. Until then, use the kit on one real job this week and keep the thread.
