How it works

One Bot. Many Coaches.
A phone that tells the truth.

Gird AI splits coaching in two. Your assistant is where the thinking happens: Coach writes your sessions, plans your cycles, and reads your history. The phone is where the doing happens: it runs the session, records what you did, and shows you the numbers. There is no chat in the app.

Who does what

Every row in your history has a clear owner. Coach never invents a session; the phone never rewrites the plan behind your back.

Coach writes

  • Sessions — the workouts, practice sessions, study blocks you'll run, saved to your Favorites
  • Development Cycles — weeks of programs scheduled toward a target date
  • Reminders — session alarms, eve-of messages, to-dos, cycle reminders
  • Coach Notes — one pinned message per Coach with the week's focus
  • Your Profile and Daily to-dos — from the intake conversation

You record

  • Sessions you completed — sets, reps, load, rounds, minutes
  • Scores — time, rounds and reps, calories, load, or a 1–10 run-through rating
  • How it felt — an RPE and a note at Finish
  • Daily check-offs and journal notes
  • Dismissing a Coach Note — so Coach knows it was read

Reports on the phone and Coach's Training Summary in your assistant are computed by the same functions. One set of numbers.

Connect Coach

Four steps, once — Grok, Claude, ChatGPT, or Cursor

Coach connects to your Gird AI account through an OAuth grant — the same sign-in as the phone. It acts as you, and only as you. Grok is the primary surface; Claude, ChatGPT, and Cursor use the same MCP plus a host prompt pack.

  1. Sign in on the phone

    Install Gird AI and sign in with the same account you will use with your assistant.

  2. Add the connector

    Pick your assistant below and add a custom connector with the Gird AI MCP URL the app shows you on its Setup screen. In Grok, open Connectors. In Claude, Customize → Connectors → Add custom connector. In ChatGPT, add the MCP server URL in developer settings. In Cursor, add it as a custom MCP server.

  3. Approve the sign-in

    Your assistant asks you to sign in to Gird AI and approve the connection. That links Coach to your account — no shared API key, and you can revoke it any time.

  4. Say “Set me up”

    Coach asks what you want from Gird AI — goals, how you like to train, everyday habits, how much it may do on its own — and saves the answers to your Profile. Skip it and finish later if you like.

Grok (primary)

  • Custom connector → https://api.gird.app/mcp
  • Complete Gird sign-in + consent as the phone user
  • Paste bots/coach/DEFINITION.md into the Bot profile; attach skills

Claude

  • Customize → Connectors → Add custom connector → https://api.gird.app/mcp
  • Leave client id/secret empty (DCR); approve Gird sign-in
  • Paste bots/coach/claude/SYSTEM.md as Project instructions

ChatGPT

  • Developer MCP → add https://api.gird.app/mcp
  • OAuth with refresh (offline_access); callback chatgpt.com/connector/oauth/…
  • Paste bots/coach/openai/SYSTEM.md as GPT instructions

Cursor

  • Add a custom MCP server → https://api.gird.app/mcp
  • Complete Gird sign-in + consent as the phone user
  • Attach the coach skills from skills/ where your plan allows
Strength Coach screen: pinned Coach Note, Today's Piece with a Start button, favorites and this week

Things to say

Talk to Coach like a coach

Coach starts every conversation by checking which Coaches you have and speaks as the one you're talking about — Strength Coach for the bar, Piano Coach for the recital. Ask for a plan, a session, a note, a nudge, or a review.

Coach passes each Coach's discipline on every action, so your Piano Coach never edits your lifting cycle.

  • Set me up
  • What should I do today?
  • I skipped yesterday — talk me into something short
  • How did my week go?
  • Add a music coach — I'm starting piano
  • Create a 5x5 squat at 80 kg and pin it to Favorites
  • I have a piano recital on the 14th — plan my practice until then
  • I'm at A2 Spanish with a trip in June — plan my Learning Cycle
  • My portfolio is due March 1 — plan a Project Cycle to get six finished pieces
  • My chemistry final is May 12 — plan an Exam Cycle
  • Pin a note on my coach's screen with this week's focus
  • Add “take supplements” to my daily todos

The daily check-in

Coach looks once a day — and mostly stays quiet

On a schedule you agree to, Coach reads a snapshot: today's piece and whether it happened, the last seven days, your coaching policy, and how many nudges it has left. It names one state — on track, skipped, stuck, re-entering — and takes one small step or none.

  • A silent morning is the normal result. Coach never schedules a second message to say well done.
  • Your policy, not its mood. Style (direct, analytical, supportive), what it may challenge you on, quiet hours, and daily and weekly caps live on your Profile.
  • Autonomy per action. Notify, reschedule a day, or swap in a shorter session you pre-approved — each is off by default, then ask-first, then automatic. You choose.
  • Already done? Dropped. A reminder for a day whose session is finished is removed on the phone before it fires.
Reminders scheduled by Coach: sessions, to-dos, eve-of-training messages

When the Bot is out of reach

Every Coach action has a manual fallback in the app: build a session, plan a cycle, set a 1RM, dismiss a note. It's the secondary path, but nothing stops working.

Offline-first

Your phone is the primary store while you train. Sessions are written locally and synced to your account when you're online; Coach reads them from there.

Your grant, your call

Coach connects with a sign-in you approve, never a shared key. Revoke it at api.gird.app/connections without signing the phone out.

Ready when you are.

Create an account, start your 14-day free trial, and connect Coach in your assistant.