sugarforever/chat-ollama

ChatOllama is an open source agentic app for running AI agents across local and hosted models.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 19th, 2026
Created on February 17th, 2024
Open Issues & Pull Requests: 250 (+0)
GitHub issues: Enabled
Number of forks: 561
Total Stargazers: 3,512 (+0)
Total Subscribers: 31 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 28
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 499 days
Stale 30+ days: 24
Stale 90+ days: 23

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (5)
  • feature (5)
  • documentation (1)
  • good first issue (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

ChatOllama is an open-source agentic app for running AI agents across local and hosted models.

ChatOllama addresses the need to interact with multiple AI providers and models through a unified command-line interface. It works by discovering available models from configured providers, maintaining an in-memory conversation, and allowing the agent runtime to call tools like file reading, directory listing, and grep operations to inspect the working directory. Users can switch between providers and models mid-conversation without losing context.

The tool suits developers who want to experiment with different AI models and providers without building custom integrations. It works well for local development workflows where agents need filesystem access. The project supports major hosted providers including OpenAI, Anthropic, Google Gemini, DeepSeek, and OpenRouter, alongside local Ollama instances. Configuration happens through environment variables, with explicit startup overrides available for provider, model, API endpoint, and credentials. The step budget for agent reasoning is configurable, defaulting to four steps per prompt.

Development activity shows consistent engagement with the codebase. The project maintains active responsiveness to issues and pull requests. Work spans across multiple areas including provider integration, CLI functionality, and agent runtime behavior. The maintainers regularly update documentation to clarify provider configuration and model selection mechanics.