What is the Joshu Hugging Face connection?

Joshu connects to Hugging Face through API tokens and OAuth, accessing the model repositories, datasets, and Spaces you authorize. It checks deployment health, tracks model card updates, verifies dataset releases, and connects machine learning workflows back to your engineering tickets. You work with an assistant who has a desk, a computer, and persistent memory, not another machine learning hub to navigate for simple status checks.

Is my Hugging Face data secure?

Yes. Every Joshu runs in its own isolated, sandboxed cloud computer. Proprietary models, evaluation datasets, and logs Joshu reads stay in that private sandbox. Joshu only accesses repositories you authorize, and your data is never used to train public AI models.

Will Joshu delete models or modify Spaces without asking?

Joshu operates in read and evaluation mode by default. Pushing model weights, updating public repository visibility, or deleting datasets follows strict approval rules you set.

What can Joshu access on Hugging Face?

Only the organizations, repositories, datasets, and Spaces authorized during token configuration. Joshu cannot view private models or internal repositories in unconnected accounts.

What is the difference between Hugging Face native tools and Joshu?

Hugging Face tools operate within specific model hubs and Spaces. Joshu is an assistant with long-term memory across Hugging Face, GitHub, Slack, email, and task boards. It connects machine learning model releases to engineering documentation and alerts you when production endpoints encounter errors.

Do I need a paid plan?

Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including Hugging Face. There are no surprise usage tiers or seat markups.

Home ConnectConnect Joshu to Hugging Face

Connect Joshu to Hugging Face

Connect Hugging Face so Joshu can check model repositories, monitor inference spaces, and track machine learning datasets.

Hugging Face

“What model repositories did our team update on Hugging Face this month?”

Joshu inspects your organization repositories, lists recently pushed model commits and README updates, and leaves a brief on your desk.

“Run our evaluation dataset against the fine-tuned classification model.”

Joshu stages the inference request via your endpoint, compiles accuracy metrics, and formats a clean comparison table for review.

“Check the deployment status and logs for our Hugging Face inference Space.”

Joshu checks the Space runtime container, flags any startup errors or memory limits, and quotes the recent log entries.

Model weights, fine-tuned checkpoints, and evaluation datasets on Hugging Face connect directly to your engineering workflow.

What Joshu does

Joshu keeps track of your Hugging Face organization to monitor model card documentation, inspect dataset versions, and check the runtime status of inference Spaces. When fine-tuning jobs finish or new checkpoints are pushed, Joshu evaluates model outputs, flags deployment failures, and drafts release summaries for your engineering team.

What you do

Connect your Hugging Face account using an API token and select which repositories, datasets, or Spaces Joshu may inspect. Decide whether evaluation runs and endpoint checks report into your daily brief or stay on call for specific queries.

Why it sticks

Monitoring open-source model repositories and Spaces across team members often requires checking multiple dashboards. Joshu inspects commit activity and container health directly so your machine learning assets stay organized.

Permissions and limits

Joshu accesses Hugging Face using scoped access tokens you generate. It reads repository metadata, checks Space logs, and submits inference calls according to token permissions. It cannot publish public models without explicit confirmation.

Frequently asked questions

: Joshu connects to Hugging Face through API tokens and OAuth, accessing the model repositories, datasets, and Spaces you authorize. It checks deployment health, tracks model card updates, verifies dataset releases, and connects machine learning workflows back to your engineering tickets. You work with an assistant who has a desk, a computer, and persistent memory, not another machine learning hub to navigate for simple status checks.
: Yes. Every Joshu runs in its own isolated, sandboxed cloud computer. Proprietary models, evaluation datasets, and logs Joshu reads stay in that private sandbox. Joshu only accesses repositories you authorize, and your data is never used to train public AI models.
: Joshu operates in read and evaluation mode by default. Pushing model weights, updating public repository visibility, or deleting datasets follows strict approval rules you set.
: Only the organizations, repositories, datasets, and Spaces authorized during token configuration. Joshu cannot view private models or internal repositories in unconnected accounts.
: Hugging Face tools operate within specific model hubs and Spaces. Joshu is an assistant with long-term memory across Hugging Face, GitHub, Slack, email, and task boards. It connects machine learning model releases to engineering documentation and alerts you when production endpoints encounter errors.
: Joshu is $95 a month with a simple flat rate. That includes your sandboxed cloud computer, a dedicated US phone number, an @joshu.me email address, eight-level cortex memory, and all tool connectors, including Hugging Face. There are no surprise usage tiers or seat markups.