Featured

Building a Fully Local, System-Wide AI Agent CLI on Linux

on
Cloud-based agentic CLI tools are undeniably convenient, but sending internal terminal workflows, system commands, and proprietary files to third-party endpoints is a persistent privacy risk. Running a fully local, autonomous agent directly on your workstation eliminates subscription costs, avoids rate limits, and grants you unconstrained access across all your attached drives. This guide details how to pair Ollama with Open Interpreter on modern Linux (Ubuntu), resolve tricky runtime quirks like Python 3.14 native builds and removed modules, map persistent storage, and create a one-click desktop launcher. System Architecture The setup consists of two layers: Inference Engine (Ollama): Serves local open-weight models with hardware GPU acceleration. Agent Harness (Open Interpreter): Interprets natural language queries, writes code, and executes Bash or Python commands directly on your system. For agentic coding and file management, qwen2.5-coder:14b provides an optimal balance of c...
0

How to Upgrade Manually to Ubuntu 26.10 "Stonking Stingray"

on
 

With the development cycle for Ubuntu 26.10 officially underway, Canonical has published stonking/snapshot-1. For early adopters, developers, and enthusiasts looking to ride the absolute edge of the open-source wave, the temptation to jump from the stable shores of 26.04 LTS, Resolute Raccoon, into the development stream is strong.

Because the automated release pathways are not populated so early in the cycle, the standard do-release-upgrade -d tool will politely decline to find the new branch. To make the leap, we must step past the guardrails and manage our repository tracking manually.
> Important Prerequisite: Upgrading to a day-one snapshot moves your environment into a highly experimental space. Ensure all core personal files, configurations, and local development repositories are thoroughly backed up before executing these steps.

Ubuntu 26.04 has transitioned to a modern, structured deb822 formatting layout for core package sources. This means standard modifications require adjusting /etc/apt/sources.list.d/ubuntu.sources rather than the traditional legacy sources.list file.

We can use the stream editor (sed) to instantly seek out every reference to the 26.04 development baseline (resolute) and shift it over to point to the new 26.10 pocket (stonking).

Open a terminal and run:
```bash
sudo sed -i 's/resolute/stonking/g' /etc/apt/sources.list.d/ubuntu.sources

With the source locations successfully modified, command APT to pull down the newly assigned package definitions from the Stonking servers:

```bash
sudo apt update

```
*Note: It is entirely typical to notice a few warnings regarding third-party PPAs or external software repositories during this step. Many independent maintainers do not publish packages for an interim cycle until it approaches its final beta stages.

Because moving between operating system versions involves changing foundational software dependencies, a standard upgrade command is insufficient. We must utilize dist-upgrade (or full-upgrade), which permits APT to intelligently add new system packages or prune obsolete components as required:

```bash
sudo apt dist-upgrade -y

```

Once the package extraction and configuration phases conclude completely, remove the remaining redundant packages left behind by the transition, then restart the machine to boot directly into the brand-new development kernel:

```bash
sudo apt autoremove -y
sudo reboot

```
Once your machine initialises back to the desktop environment, you can confirm the underlying system metadata has settled correctly by querying the Linux standard base information helper:

```bash
lsb_release -a

```
Your terminal should display a successful update to Ubuntu Stonking Stingray (development branch), ready for testing the newest iterations of system utilities and upstream components.

Comments

Post a Comment