Guide
Hobbit is an AI agent
It does more than answer. It reads your team, uses tools, runs whole jobs through, and asks before every change. This page explains what agent and workflow mean inside Hobbit.
Most "football AI" is one of two things: a chatbot wearing a football prompt, or a library of templates. Hobbit is a third thing: an agent. You give it a job, it goes and reads what it needs and does what needs doing, and it stops to ask you at the points that are yours to decide.
An agent is not a chatbot
A chatbot only talks. Ask "what should we train on Wednesday" and you get generic advice, because it has no idea whether you train on Wednesday, which team, or what you did last week.
An agent acts. Same sentence, and Hobbit first reads your calendar (the answer shows "Calendar · 3 events" above it), finds Wednesday's U10 session, reads that team's profile and last week's debrief, then shows a confirmation form to settle the player count and pitch, generates the plan, and attaches it to Wednesday's square.
The difference is those middle steps: it has eyes (it reads your data), hands (it changes your data), and a boundary (it asks before changing anything).
What happens in one turn
- Understand: is this a question, a task, or a passing remark to remember.
- Think: on a hard question it thinks first; "thought for N seconds" shows above the answer, and you can open the reasoning.
- Read: when it needs facts it calls a tool, and every read leaves a trace in the answer.
- Confirm: to change data it shows a confirmation card saying exactly what it is about to do; nothing happens until you press "Confirm", and "Cancel" drops it.
- Act and answer.
Every tool call is visible. You always know what it looked at and what it changed.
What it can read
| Data | Example |
|---|---|
| Calendar | "how many matches this week" |
| Roster | "how many left-footers in the U8s" |
| Session library, including a full plan | "what was the third block of the last passing session" |
| Match records | "our record against the Whales this season" |
| Attendance | "how many times has Sam come this month" |
| Debriefs | "what did the last three debriefs keep mentioning" |
| Uploaded files | "what does our curriculum say for week three" |
| Team profile and memories | "what is our team's philosophy" |
| Fee accounts and income | "who is due to renew", "how much came in this month" |
| The web | with web search on it searches, and reads a URL you paste |
What it can do
| Action | Example | Notes |
|---|---|---|
| Add, change, delete events | "training every Wednesday at 7pm at North Park until December" | Weekly repeats, venue, per-event cost |
| Take attendance | "Sam was excused today, everyone else came" | Late, waived, whole session not charged |
| Record a result | "won 3 to 2 against the Whales on Saturday, at home" | Opponent, home or away, score |
| Generate a parent preview | "write a preview for Friday's training" | Reads the plan, philosophy and recent training |
| Create a team | "create a U9 team called the Cubs" | |
| Remember something | "remember, this team only has half a pitch on Thursdays" | Goes to the team memory; edit or delete in the team brain |
| Generate a whole session | "plan Wednesday's training" | Confirmation form first |
| Draw a drill diagram | "draw a 3v3 with two floaters" | Edited by conversation |
Every action that changes data shows a card first. It never touches your team without you knowing.
Workflows: it takes on the whole job
Tools are the means; workflows are the end. A coach does not want "it can read the calendar"; a coach wants "get next Wednesday's training ready". In Hobbit that is a workflow: the agent chains several tools and runs the job through, stopping only where the call is yours.
Planning a session: "plan next Wednesday's training for the U8s". It reads the calendar and finds that training, sees the square has no plan yet; reads the session history to know what the last three weeks covered and where this one should progress to; reads the recent debriefs to carry last time's weak point into this session; shows the confirmation form for you to check numbers, pitch and standard; generates; saves to the library. Say "attach it to Wednesday's training" and it hangs on that square, and it can go on to generate the parent preview.
A training day: bind the session, generate the preview, take attendance, speak a one-minute debrief, and the recap and next focus come out by themselves. This workflow has its own screen, the coach workspace: every step of the day laid out in order, and whatever is undone visible at a glance.
A match day: set the starting lineup, pre-match preview, record the result and each appearance, debrief, post-match recap, memory update. Also on the workspace.
Recruitment and camps: build a sign-up form, share the link, parents fill it in without an account, the list imports into a team in one click, and the first session can be generated. From a poster to a team that can train, with nothing carried by hand in between.
End of term: read each child's real attendance and appearances, draft the comments one by one, print them as certificates, with portraits from the team photographer.
Fees: attendance deducts session credits, a balance below the threshold lands on the renewal list, and the income panel totals it by month and by team. You do one thing: take the roll.
A workflow keeps the same boundary as a single action: reads leave a trace, changes are confirmed. A longer workflow never means it decides more on your behalf.
It does not live only in the chat box
The chat is the front door, but the same agent works in every corner of Hobbit, carrying the same team brain:
- Session design: settles the framework, works through each block, writes the detail, draws the diagrams; one plan is dozens of reasoning steps.
- Session standards: reads the structure out of a plan you upload.
- Drill diagrams: turns a sentence or a sketch into a vector diagram.
- Previews and recaps: reads the plan, the philosophy and the debriefs, and writes for parents.
- Voice debrief: shapes your spoken minute into four parts, then distils the team's memories across debriefs.
- Player reports: reads real attendance and appearances and drafts the comment.
- AI roster import: recognises player fields in a spreadsheet or a group chat screenshot.
- Write, design, photographer: match reports, posters, portraits.
Whichever page you are on, it is on that page doing that step for you.
What it remembers, and what it does not
It remembers the team brain: profile, roster, calendar, session history, the notes you gave it, the memories it distilled from debriefs, the files you uploaded. Those persist across conversations; a new chat knows your team just as well.
It does not turn every chat into memory by itself. To make it remember, say "remember..." and it shows "Add to this team's AI memory?" for you to confirm. See the team brain section of How Hobbit works.
What it does not do
- It does not decide for you: every change is confirmed first.
- It does not run on its own: it never generates a session or a preview you did not ask for.
- It contacts nobody: it sends nothing to parents, players or opponents; the public page is a link you share.
- It collects no money: the fee account only keeps records.
- It does not guess teams: team names are opaque and the age group field is the authority; with several matching teams it asks rather than guesses.
How to talk to it
- Name the team: "plan a session for the Eagles U10" and it reads the Eagles U10 first.
- State the conditions: numbers, pitch, duration, equipment, all at once, and the confirmation form needs no edits.
- State the constraints: "no cones", "work on two-touch play"; what is agreed in the chat travels into the generation.
- Give feedback: "too easy", "make it 5v5"; it changes one block and leaves the rest.
- Show it things: a whiteboard photo, a PDF plan, a match screenshot, straight into the box.
- Tell it to remember: one "remember" and you never repeat yourself.
Which model it runs on
State-of-the-art models, with the highest reasoning effort for session generation. On top of the model Hobbit adds three things: the DGC method (how every session is designed), the team brain (it knows your team), and tools with confirmation cards (it can act, you decide). Models will change; those three will not.