Skip to content
AgentsFS Hub
Sign in Request access

Optional hosted layer for AgentsFS

Your AgentsFS knowledge bases, readable on the web.

Push a local knowledge base, browse and edit its Markdown, follow links and history, then pull the complete Git repository whenever you want.

The Hub stores real Git · The files remain the source of truth

Private by defaultExplicit Git syncClone anytime

Workspace preview

The same knowledge base, presented for people.

Browse a described file tree, read rendered Markdown, follow selected backlinks, edit text files, and inspect the Git commits behind each note.

Insurance claimdemo / insurance-claim
Private
Markdown noteGit history
projects / water-damage-claim / status.md verified Jun 10

description: Current state and next actions

Current state2 declared sources

Claim status

Current state, supporting evidence, and the next action in one Markdown note.

Claim
GM-2026-88341 · Granite Mutual
Event
Burst supply line · May 18, 2026
Insurer estimateContractor quoteGap to close
$11,200$19,750$8,550

Working position

Coverage is accepted. The unresolved issue is valuation: the policy is replacement-cost, while the carrier estimate depreciates the cabinets.

Next action

By Jun 20: send the dispute to Dana Whitfield with the BlueOak Builders quote and policy §4.2.

Illustrative Markdown renderingHistory availableText files editable

Showing status.md

8f2c1aclarify claim status and response deadline2 minutes ago
Illustrative Hub workspace Select a filename to view another ordinary knowledge base file.

The workflow

Push with the CLI. Work in the browser. Pull with Git.

The Hub is a normal remote in the AgentsFS workflow. Commit locally, push when you want the Hub updated, and pull a checkout wherever you need one.

01

Connect and push

Send committed work to your private namespace.

Create an account and access token, sign the CLI in once, then push from the AgentsFS root. Later pushes send later commits.

afs hub login
afs hub push insurance-claim
02

Browse and edit

Use an AgentsFS-aware workspace.

Follow descriptions, wikilinks, backlinks, and the knowledge graph. Owners and write collaborators can edit text files; every save is a Git commit.

Markdown · backlinks · graph · history
03

Pull a checkout

Bring the complete repository anywhere.

Pull by repository name. The first run clones it; later runs fast-forward the existing checkout when the history has not diverged.

afs hub pull insurance-claim
git log --oneline

Why use the Hub?

Git hosting stores the repository. The Hub understands the knowledge layer.

AgentsFS works with GitHub, GitLab, self-hosted Git, or no remote at all. Use the Hub when you want a web interface built around AgentsFS conventions without changing the repository format.

Generic Git remote

Stores files and commits.

  • Clone, pull, and push
  • General-purpose repository browser
  • Normal Git permissions and history
AgentsFS Hub

Understands how the knowledge connects.

  • Described file tree and freshness
  • Resolved wikilinks and backlinks
  • Interactive knowledge graph
  • Repository images inside Markdown
  • Browser edits saved as Git commits

Portable by construction

The Hub is a remote, not the database.

Keep using the Hub, move to another Git remote, or run a Hub on infrastructure you control without converting the knowledge base.

01 / Private first

New knowledge bases start private.

Only the owner and collaborators they add can read them.

02 / Deliberate sharing

Public means explicit.

Publishing exposes the files and Git history, and requires confirmation.

03 / Complete exit

Pull or clone whenever you want.

The files and commit history leave without data conversion.

04 / No silent sync

Copies change only when pushed or pulled.

There is no hidden background synchronization state.

Optional hosted agent

A hosted agent can work across your Hub knowledge bases.

When enabled, the Hub gives you access to a shared hosted agent, scoped to your account's own permissions — it can read the knowledge bases you have access to, answer from their notes, and commit changes through Git on your behalf. The Hub stays the authority for identity and permissions; the local AgentsFS core does not depend on it.

Bring an existing AgentsFS knowledge base

Keep working locally. Add the Hub when the web view is useful.

AgentsFS works without an account. Create a Hub account only when you want hosted Git, browser access, and optional collaboration.