Define its personality.
Choose each companion’s look and how it participates: proactive, a listener, or speaking only when asked.
Your team and agents build on past decisions, solutions, and lessons learned to solve problems and move projects forward, without rebuilding context in every conversation.
How can I help today?
CONTEXT THAT MOVES WORK FORWARD
Connect your AI tools and agents to Gomind.
Bring context together in collections and choose who can access it.
Use what has already been learned to move the next task forward.
Save new decisions and discoveries in shared memory.
The next task starts with more context.
Bring your knowledge to the meeting, with you or on your behalf. Your Companion listens, speaks with authorized context, and brings back decisions and next steps.
Choose each companion’s look and how it participates: proactive, a listener, or speaking only when asked.
It follows the meeting and joins by voice, bringing your context to the conversation in line with the personality you define.
Choose what it can bring to the meeting and share, and what stays private. It consults you when needed.
Receive the transcript and decisions, with next steps organized. Review what to save and share after the meeting.
What one person learns can help the next conversation. Gather decisions, discoveries and knowledge in collections your AIs can consult.
Keep knowledge in Gomind and retrieve relevant facts for each question. Send less repeated history to your AI.
Share context with the people who need it. You choose who joins each collection and who can read or add knowledge.
The next conversation can pick up where work left off. Your AI consults authorized context to help you move forward.
Camila records the agreements. Bruno updates the scope. Pedro finds it all in the same memory.
Connect the tools people already use. Share context through collections, with the access that makes sense for your team.
Explore connectionsBring project context into your applications and agents. Connect Gomind's shared memory through SDKs, the API or MCP.
Read the developer quickstartOrganize memory by organization and collection.
Remember, recall, or delete facts with the corresponding permissions.
Use MCP tools to consult and record information as work progresses.
npm install @gomind/sdkimport { GomindClient } from '@gomind/sdk';
const memory = new GomindClient(
'https://api.gominddb.com',
process.env.GOMIND_API_KEY!
);
await memory.remember(
'project:aurora', 'delivery_day', 'friday'
);
const { facts } = await memory.recall('project:aurora');
console.log(facts);
go get github.com/ingate/[email protected]package main
import (
"context"
"fmt"
"log"
"os"
gomind "github.com/ingate/gomind-go-sdk"
)
func main() {
memory, err := gomind.NewClient(os.Getenv("GOMIND_API_KEY"))
if err != nil { log.Fatal(err) }
ctx := context.Background()
_, err = memory.Remember(ctx, "project:aurora", "delivery_day", "friday", "")
if err != nil { log.Fatal(err) }
result, err := memory.Recall(ctx, "project:aurora", 20)
if err != nil { log.Fatal(err) }
fmt.Println(result.Facts)
}
composer require ingate/gomind-php-sdk<?php
require 'vendor/autoload.php';
use Ingate\Gomind\Client;
$memory = new Client(getenv('GOMIND_API_KEY'));
$memory->remember(
'project:aurora', 'delivery_day', 'friday'
);
$result = $memory->recall('project:aurora', 20);
foreach ($result->getFacts() as $fact) {
echo $fact->getObjectOrValue();
}
export GOMIND_API_KEY="your-api-key"# Store a fact
curl https://api.gominddb.com/v1/remember \
-H "Authorization: Bearer $GOMIND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"subject": "project:aurora",
"predicate": "delivery_day",
"object": "friday"
}'
# Recall it in another session
curl https://api.gominddb.com/v1/recall \
-H "Authorization: Bearer $GOMIND_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "project:aurora", "limit": 20}'
Shared memory
Access levels: read and write
Steps: account, collection, connection
Ways to keep going
Encryption, HTTPS/TLS and hashed credentials. Responses exclude authentication secrets and payment details.
Boundaries per organization and collection. Read and write access for your team and authorized partners.
Delete facts and collections with the appropriate permission. You decide what remains available.
Context, source and date in records. Action traces and identifiers help track operations and investigate failures.
No. Each person can connect one or more compatible AIs to Gomind. To share the same project memory, those connections need access to the same organization and collection.
Summaries are produced by the AI that consults Gomind. Ask for one in a conversation, or configure a routine if your bot supports it. Gomind provides shared memory; retrieval, summaries, and scheduling depend on the connected tool.
Connecting provides tools for recording and consulting information. Ask your AI to use Gomind and check what was saved. Chat history is not automatically imported.
The connection guides explain setup in compatible AI apps. SDKs and the API are available for custom integrations.
Meeting decisions, client agreements, project learnings and useful references. Organize this knowledge into collections and choose what to share with each group so others can continue the work.
Create your account, organize a collection and connect a compatible AI. Then gather the context you want to share and set access for the people who will continue the work with you.
A fact is one unit of memory: a relationship between a subject and another entity or value. For example: project → uses → PostgreSQL. It can represent a decision, a preference, or a piece of knowledge about the project.
No. A message or document can contain several facts. Gomind stores the relationships you or your agents send, so they can be connected and consulted later. It does not automatically import every conversation.
Facts measure stored memory; credits are consumed by operations. A single operation can work with several facts. Additional credit packs increase usage credits, without changing the plan’s fact limit.
A collection groups facts inside your organization. Use one for each project, product, or client, and define its participants and permissions. Connected AIs with access to the same collection can consult that shared memory.
Yes. With write permission, you can remove a fact or the facts associated with an entity. You can also delete a collection when you have permission to do so. This removes information from Gomind; it does not erase copies already returned to another tool.
The people invited to participate, according to their permissions. Define who can read information and who can also write.
Yes. External professionals can participate in the collections they are invited to, with permissions matching their role.
Connected context. Continuous work. Carry your team’s decisions and solutions from one AI to another, with control over who can access and contribute to that knowledge.
Start for free