<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>AI on Public Notes</title>
    <link>https://blog.cue4net.com/tags/ai/</link>
    <description>Recent content in AI on Public Notes</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 22 Sep 2024 20:51:56 +0200</lastBuildDate>
    <atom:link href="https://blog.cue4net.com/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Ollama With VSCode and Continue Extension</title>
      <link>https://blog.cue4net.com/posts/using-ollama-with-vscode/</link>
      <pubDate>Sun, 22 Sep 2024 20:51:56 +0200</pubDate>
      <guid>https://blog.cue4net.com/posts/using-ollama-with-vscode/</guid>
      <description>Introduction This post is a continuation of post 🖇Ollama AI as a Network Service, where I described the setup of Ollama as a network service. In this post, I will show you how to integrate VSCode and the Continue extension to create an AI-powered toolchain for your software development needs.&#xA;Installing VSCodium on Linux I prefer the telemetrie free version of VSCode called link vscodium.com over the Microsoft version because it is more lightweight and does not require a telemetry service to work.</description>
    </item>
    <item>
      <title>Ollama AI as a Network Service</title>
      <link>https://blog.cue4net.com/posts/ollama-as-network-service/</link>
      <pubDate>Sun, 15 Sep 2024 05:06:09 +0200</pubDate>
      <guid>https://blog.cue4net.com/posts/ollama-as-network-service/</guid>
      <description>Enabling Seamless Integration with Ollama as a Network Service Developed by the same team behind the innovative llama models, Ollama offers a unique advantage: compatibility with LocalAI API in its later versions. This means that Ollama can be seamlessly integrated into various LLM (Large Language Model) integration applications, such as Nextcloud Assistant or the Continue plugin for VSCode and IntelliJ.&#xA;For my own installation process, I opted for a Docker-based approach.</description>
    </item>
  </channel>
</rss>
