hyreflow docshyreflow docsDocumentation

Second brain

The notes Hyreflow keeps about your business, and how your agent reads them before it asks you anything.

Your second brain is a set of notes Hyreflow keeps for your workspace: who you recruit for, the ideal customer, the roles you hire for, and how you like your outreach to sound. Your agent reads it before it asks you about your business, so you answer each question once.

The build and the Knowledge page come to new workspaces first, and to older ones later. Every workspace's agent has the tools below already: in an older workspace the notes start empty, and your agent adds the ones you tell it to.

What gets built

Hyreflow reads your company's website and writes the first notes. It reads the website saved for your workspace (the one you type on the setup page), else the site at your work email's domain (for [email protected], acme.com). If you signed in with a personal email such as Gmail, Hyreflow asks you for the website first. The notes cover:

  • the ideal customer and the roles you recruit for
  • a profile for each type of candidate you place, with the search filters that find them
  • the pains, hiring triggers, outreach angles and proof points for each profile

Each note is a short page. Notes link to each other with [[wikilinks]], so a candidate profile can point at the role it belongs to. The build runs in the background and shows its progress on the setup page. A workspace holds up to 500 notes of up to 64 KB each.

Who gets it

Everyone in the workspace reads the same notes, and no other workspace can read them. The build starts when the workspace owner finishes the first step of the setup page, with the website they typed there. If the workspace was set up earlier and has the second brain switched on, the owner gets a Build my second brain button on the Knowledge page instead, with a box for the website when there is no company site to read yet. Either way, a workspace gets one build, and each person gets one build across the workspaces they own. If a build fails before it reads your site, the owner can try again an hour later.

The Knowledge page

Knowledge in the dashboard (g then r) shows every note as a list you can search and filter, and as a map of how the notes link to each other. Open a note to read it with its sources and the notes that link to it. Each folder shows when one of its notes last changed, and folds shut when you click its name. Each note says whether it was built from your site, added by an agent or edited since, and when. To change a note, ask your agent (below).

How your agent uses it

Connected over MCP, your agent is told to check your own ICP.md first when you keep one, then the second brain:

  1. hyreflow_knowledge_index lists the notes.
  2. hyreflow_knowledge_search finds the ones about a topic.
  3. hyreflow_knowledge_read opens one.
  4. hyreflow_knowledge_write changes a note, or adds one.

All four are free. The first three only read. Your agent writes a note only for something you said or confirmed, and shows you the change first: for example "We don't place SREs, we place platform engineers." Anyone in the workspace can ask their agent to change a note, everyone's agent sees the change at once, and there is no undo. To take a note out, ask for it to be archived.

In onboarding, when the build is ready, your agent confirms the top candidate profile with you and runs your first search from that profile's search filters. While it is still running, your agent asks you instead. Try "Show me what Hyreflow learned about my business."

The recruiting playbooks use your own ICP.md when you have one, then the second brain's ideal customer, and ask you only when there is neither.