iam-veeramalla/claude_with_ollama.md

Last active March 16, 2026 16:17

Star (47) You must be signed in to star a gist
Fork (28) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/iam-veeramalla/d0f46791619b0db348d8312060a80f2d.js"></script>
Save iam-veeramalla/d0f46791619b0db348d8312060a80f2d to your computer and use it in GitHub Desktop.

Download ZIP

claude code integration with ollama to use local models

Raw

claude_with_ollama.md

Run Claude with the power of Local LLMs using Ollama

Install Ollama

curl -fsSL https://ollama.com/install.sh | sh

Pull the Model

ollama pull glm-4.7-flash # or gpt-oss:20b (for better performance)

Install Claude

curl -fsSL https://claude.ai/install.sh | bash

Run Claude with Ollama

ollama launch claude --model glm-4.7-flash # or ollama launch claude --model glm-4.7-flash gpt-oss:20b

nipodemus commented Mar 13, 2026

I tried it but claude can't see the local filesystem not even the files in the directory I run it from.

I had same problem. Check /permissions, by default almost all usable are denied. I added for example Bash to Allow rules and file access started working.

medake commented Mar 16, 2026

Hi @iam-veeramalla @ShubhmPatil @chinthakindi-saikumar - I am running Windows with PowerShell and set up Ollama with the local model qwen3.5:9b. I am not able to create or read or write the files in the project directory. After a lot of serch I found that Claude’s agent capabilities (filesystem tools, project scanning) exist only in Claude Code CLI, which requires Anthropic authentication and billing. Under Ollama-only execution, Claude behaves as a plain LLM without tool access, so automated codebase analysis is not possible. How did it work in your case?