Memory and skills
What Gini remembers
The difference between the message it just read, what it keeps, and what it never stores at all.
Three different things get called "memory" and they behave differently. Worth separating, because the answer to "does Gini store our Slack messages?" is no, and the answer to "will it remember what I told it last month?" is yes.
The conversation in front of it
While a job is running, Gini has the thread, the channel it's in, and what it needs to do the work. That's working context. When the run ends, it's gone.
This is why a DM has less context than a channel, and why a follow-up in the thread is cheap while re-explaining in a new thread is not.
What it keeps
Facts about how your company works, in the wiki. Decisions, ownership, vocabulary, processes, and anything you told it to write down.
This is durable, readable and editable. It's the thing that makes month three better than month one.
What it doesn't keep
Message content it wasn't asked to keep isn't stored. Gini reads a channel to do the work and to learn what's durable from it; the raw messages don't get retained on our side.
Run records (the steps, tools called, and approvals for each job) are kept 90 days by default, so you can go back and see what happened. Enterprise plans can set a different window.
Your data never trains a model
Your messages, files and connected data are never used to train models, ours or anyone else's. That's contractual, not a setting you have to find. See Data handling.
Teaching it something on purpose
Say it. In a channel or a DM:
Revenue always means net of refunds.
Sam owns anything touching the data pipeline.
We never contact a customer without the account owner cc'd.
When I say "the deck" I mean the Series A deck in Drive.
Gini writes these down and applies them from then on. You'll notice it most in the things you stop having to say.
Making it forget something
@Gini forget what I said about the acquisition.
@Gini that page about the on-call rota is wrong. Delete it.
Or open app.ginicomputer.com → Wiki and delete it directly. Deletion is deletion, not hiding.
For deleting everything, see Deleting your data.
What's shared and what isn't
Within your workspace, the wiki is shared. That's the point: a fact one person taught Gini helps everyone.
Between workspaces, nothing crosses. Each customer runs isolated. Nothing Gini learns at your company reaches another, ever, in any form.
Your connections are yours. Teaching Gini a fact is shared. Connecting your Gmail is not: it acts with your Gmail access only when the work is yours. See How connections work.
Assume the wiki is readable by your team
Anything you tell Gini in a channel can end up in a page your colleagues can read. That's correct behaviour and it's occasionally not what someone intended. If it shouldn't be shared with your team, don't teach it to Gini.