No. Your dot installs the Fulcra CLI on its cloud computer. You only open the sign-in link it sends you and approve the connection.
On the dot's cloud computer, where the CLI saves them so it can keep working. The prompt asks your dot to tell you the exact location and never print the credentials in chat or documents. To stop access, use your Fulcra account's access controls or ask Fulcra support. Deleting the local credential file doesn't revoke access on Fulcra's side.
Yes, if both are connected to the same Fulcra account. Have the dot write results to a fixed path, such as /agents/dot/notes.md, and ask ChatGPT to read it. See Share state between a scheduled agent and your interactive agent.
It runs fulcra data-updates with a time window, which lists the records and files that changed. It then reads only those. See How an agent finds out what changed since its last run.
Yes, if you both opt in. Ask your dot to use Fulcra to connect to your colleague. Each side shares only a message channel. See How can my AI agent and a colleague's agent work out a task together?
Yes. Your dot leaves a message as a Fulcra file or record, and your other agents pick it up when they next run, so none of them need to be online at the same time. Read the full answer.
Yes, through a Fulcra share. Their agent can read only what you shared, can't write to your data, and loses access when you delete the share. Read the full answer.
Yes. Your dot creates a custom data type in Fulcra once, records a value for each new reading, and reads the history back to chart it. Read the full answer.
Sharing context with an AI — letting it know about you, your work, and your world — should be a two-way door. Grant access. Revoke it. Change agents. Keep the context. Keep what your agents make.
Fulcra was built by founders with 15 years in security infrastructure including HUMAN, Veracode, Verisign. Your vault is encrypted at rest and in transit, with per-agent scoped access and a full audit log on every read.
Agent access is kept in check · Full read audit log · One-tap revoke · Encrypted at rest and in transit · No shared passwords · HSM-backed token provisioning
.png){kind=logo}
