feat(blocks): Ollama - Remote hosts

[Fried-Squid]

Background

Currently, AutoGPT only supports ollama servers running locally. Often, this is not the case as the ollama server could be running on a more suited instance, such as a Jetson board. This PR adds "ollama host" to the input of all LLM blocks, allowing users to select the ollama host for the LLM blocks.

Changes 🏗️

• Changes contained within blocks/llm.py:
  • Adding ollama host input to all LLM blocks
  • Fixed incorrect parsing of prompt when passing to ollama in the StructuredResponse block
  • Used ollama.Client instances to accomplish this.

Testing 🔍

Tested all LLM blocks with Ollama remote hosts as well as with the default localhost value.

Related issues

#8225

[CLAassistant]

All committers have signed the CLA.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 Security concerns Potential remote code execution: The addition of the ollama_host parameter allows users to specify arbitrary hosts for Ollama connections. If not properly validated and sanitized, this could potentially be exploited to connect to unintended hosts or execute arbitrary code. It's crucial to implement strict input validation for the ollama_host parameter to ensure only authorized and safe connections are allowed.

⚡ Recommended focus areas for review Potential Security Risk The ollama_host parameter is set with a default value of "localhost:11434". This could potentially allow users to connect to arbitrary hosts if not properly validated. Error Handling The changes introduce new network calls to potentially remote Ollama hosts, but there's no visible error handling for network-related issues. Code Duplication The ollama_host parameter is added to multiple Input classes, which could lead to duplication and maintenance issues.

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	849e23d
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/675b72f29fe1a200080010db

[Bentlybro]

This is a super nice change and its much needed 🙏 once CI tests pass it should be good to go!

[Fried-Squid]

CI/CD all passing now 😄
Just forgot to run the formatter and change a type lol

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[ntindle]

@Fried-Squid can i get that cla signed so we can work towards merging this

[Fried-Squid]

Hey, not sure why but the CLA has pulled the wrong emails, those are my old work credentials and I no longer work there, is there an easy way to fix this? Have signed it on my main one

…

On Thu, 10 Oct 2024, 17:41 Nicholas Tindle, ***@***.***> wrote: @Fried-Squid <https://github.com/Fried-Squid> can i get that cla signed so we can work towards merging this — Reply to this email directly, view it on GitHub <#8234 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMALLRQLXAALRVIJW5JGFMTZ22U5DAVCNFSM6AAAAABPEHQZB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBVGU4DQNRRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ntindle]

Somewhere you’re developing probably has an old git config that contains those emails as a default. Ex GitHub.com uses one of those when you update from master or your dev machine has its git config email set to an old email.

You can reopen the PR with the correct emails after fixing locally or maybe try force pushing over but I’m not positive that force pushing to your branch will work

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[Bentlybro]

Tested and this works.