Connect a Git repository (GitHub, GitLab) as a first-class knowledge source for the Fibi AI Agent, so that training content is maintained where the documentation already lives.
Requested behaviour
Connect one or more repositories and select file patterns (for example docs/**/*.md).
Re-index on push, and show the diff between the previous and current version of each training file so reviewers can see exactly what changed.
Preserve manual edits made in Featurebase across re-indexing, rather than overwriting them.
Report per-file index status so a failed file is visible without opening every entry.
A customer evaluating Featurebase raised this after comparing with Gleap's Code Repositories feature, where a connected repo generates knowledge entries automatically on each re-index and manual edits are kept.
Today the Training Data API and MCP make this possible to build from the customer side using stable externalId values, but there is no native connector, no change detection and no diff view.
Related: Source Markdown Files from Git Repositories (Help Center scoped) and APIv2 for Fibi Training Data Management.
Please authenticate to join the conversation.
In Review
Fibi AI Agent
Integrations
44 minutes ago

Stefan Pasel
Get notified by email when there are changes.
In Review
Fibi AI Agent
Integrations
44 minutes ago

Stefan Pasel
Get notified by email when there are changes.