HeapFileAI

Connector compatibility

See what HeapFile can connect to.

Some connectors work today. Some need account setup or admin approval. Others are listed so you know they are planned, not live. Each card says what HeapFile can read, where the data travels, and what it will not do.

Provider boundary

Provider names identify systems HeapFile can work with or is evaluating for compatibility. HeapFile is not affiliated with, endorsed by, or sponsored by these providers unless explicitly stated. Availability depends on the HeapFile release, provider terms, account plan, organization policy, authorization, and configuration.

Privacy boundary

HeapFile is local-first, not local-only. Local sources and eligible local model routes can remain on the device. A cloud connector contacts its provider only through a route the user or administrator authorizes. The product identifies the permission level and data route before connection.

Authorization boundary

Ready describes release maturity. It does not grant write permission. The GitHub connector is read-only and runs one way: a repository owner installs the HeapFile GitHub App on repositories they choose, and only that owner's HeapFile can read them. Installing it never exposes HeapFile source code and never shares your repositories with other HeapFile users. It does not publish posts, deploy a site, administer repositories, or reuse chat-client authorization. Match the permission scope and data route to the task before connecting a source.

HeapFile-owned connectors are separate from ChatGPT, Codex, Claude, browser tabs, local CLI state, and local checkouts. Chat-client connectors do not authorize HeapFile. A listed connector is not an authorized connector.

HeapFile first

Every coding agent starts warmer. Compatible clients should call prepare_work before broad searches or vendor connectors. If HeapFile needs client evidence, the client supplies only data it is already authorized to access.

GitHub and AWS

GitHub and AWS use explicit HeapFile configuration and authorization. The GitHub App is read-only and one-way: you install it on repositories you own, and only your HeapFile reads them. It never exposes HeapFile source code. Local git, a GitHub App installation, local AWS login, and chat-app connectors are separate routes; unavailable routes are reported honestly when they are not configured.

ReadyWorks in the current release after you choose the source or install the app.
PreviewBuilt or documented, but still needs controlled setup or final release proof.
CatalogedOn the roadmap. No live access in this release.
ResearchBeing evaluated. No live connector is available yet.

Default view

Ready now

This deviceLocal files

Choose explicit safe workspace roots.

Maturity
ready
Authorization
local-setup
Permissions
local-access, read-only
Data route
on-device
Release
current-release
Last verified
2026-10-03

Uses: Selected local files and documents.

Does not: Crawl the whole home folder by default.

This deviceLocal Git

Use repositories already present on this device.

Maturity
ready
Authorization
local-setup
Permissions
local-access, read-only
Data route
on-device
Release
current-release
Last verified
2026-10-03

Uses: Local repository history, diffs, branches, and file evidence.

Does not: Authorize hosted Git providers.

This deviceMCP tools

Register HeapFile MCP with a compatible local AI client.

Maturity
ready
Authorization
local-setup
Permissions
local-access
Data route
on-device
Release
current-release
Last verified
2026-10-03

Uses: Work Memory, Handoff Packs, and local HeapFile tools.

Does not: Force every client to call HeapFile automatically.

This deviceOllama local AI

Install and run an eligible local model route.

Maturity
ready
Authorization
local-setup
Permissions
local-access
Data route
on-device
Release
current-release
Last verified
2026-10-03

Uses: Local model route for bounded local reasoning.

Does not: Imply all model providers or mobile local models are supported.

Developer systemsGitHub

A repository owner installs the read-only HeapFile GitHub App on repositories they choose. heapfile.com checks that the install belongs to that owner's account, and only that owner's HeapFile reads the selected repositories through short-lived read-only tokens.

Maturity
ready
Authorization
setup-required
Permissions
read-only
Data route
provider-api
Release
current-release
Last verified
2026-10-03

Uses: Read-only evidence from the repositories you select: issues, pull requests, commits, releases, workflow runs, and checks. Access flows one way, from your repositories into your own HeapFile.

Does not: Expose HeapFile source code, share your repositories with other HeapFile users, or request write, administration, webhook, secret, or deployment permissions.

Mobile status

Mobile is a companion surface, not a connector.

Phones and tablets are for capture, selected recall, approval review, and handoff. Public store availability depends on store review and release status, so mobile is described separately from provider connectors.

Current roleLow-power capture, recall, approval review, and handoff.
BoundaryNo broad connector crawls, heavy local model jobs, signing keys, or cloud credentials on mobile.