What the onboarding program reads

The onboarding program runs on your computer: in the gogoportal skill's script, which your tool runs (see the connector; on claude.ai, in Claude's own sandbox), or in the local connector's draft_lessons. Both follow the rules on this page.

Only the files your tool names

The program never reads your project folder on its own. Your tool writes the takeaways, in its own words. Lessons need no folder: for them the program reads only the lessons it kept and your client list. Your tool may also name files to go with them, by their paths inside the project, and only files you named; the program reads only those, and by default none. The skill takes the project from the folder your tool works in; the local connector takes the folder your tool passes with that call, and never picks one itself.

How each named file is checked

On your computer, before anything is sent. A file is refused, by name, when it is:

• Outside the project, or reached through a link. The program never follows a link.
• Hidden: its name, or a folder on its path, starts with a dot (.git among them).
• Named like a key or password file (.env, id_rsa, *.pem, keystores).
• Listed in .gogoportal-private at the top of the project, or in a folder listed there.
• Empty, larger than the program takes, or not text.
• Holding something that looks like a key, a password, a token or a connection string.
• Holding personal data: email addresses and phone numbers.
• Naming one of your clients or a term that identifies the project, in its text or its path. Your tool gives the ones it knows; you can also list client names, one per line, in .gogoportal-clients at the top of the project (with the skill, a list in a folder above it counts too).

A refused file stays out: nothing is prepared with it, and your tool never edits a file to make it pass. The program reads .gogoportal-private only to check a file your tool names.

# .gogoportal-private: one path or pattern per line
notes/clients/
contracts/*.md
**/invoice-*.txt

In what your tool writes, secrets, personal data, full paths, IDs, and the client names and terms it gives are replaced with [removed] before anything is sent. The terms that identify the project also go with it, so the site's final check refuses any part that still holds one. The site searches for them and does not store the list. Your client names stay on your computer.

What it asks your tool for

• The takeaways: only what the Agent doesn't already have, each written to stand without your project.
• When each takeaway was learned, and the versions of the tools it applies to.
• What each cost to learn: from the logged usage of the sessions involved where logs exist, an estimate only where they don't, marked so.

The stamp

The skill stamps what it cleaned with its version and a fingerprint of the batch, and your tool passes the batch on as it is. The site refuses a batch with no stamp, one changed after it was stamped, and one the same cleaning would still change, before it keeps anything of it. That stops lessons going out uncleaned by mistake. It does not prove more: an agent that fakes a stamp on purpose is caught only for what the site can see, which leaves out your client names. See the stamped batch.

What it tells you

Your tool tells you in one line what it sent, with the link to your sign-off page; it cannot sign off. Approvals happen on the site, not in the chat: on your sign-off page you read every item and file as it will be shared, and what it cost to learn. That figure earns nothing, and you can correct it or leave it out when you sign off. Nothing goes live until you sign off.

The site checks again

The site does not rely on the program. Its final check refuses a file with a secret and does not store it, and refuses a package with more than 10 pieces of personal data. Material refused as not accepted keeps only its hash and report for 30 days. If you withdraw a shared project later, its content is deleted within 24 hours.