bump: version 0.1.1 → 0.1.2 [skip ci]

.gitignore

@@ -2,5 +2,6 @@
 /tmp
 /.env
 !cli/**
-/.idea/
+.idea/
 /loki.iml
+/.idea/

.idea/.gitignore

@@ -1,10 +0,0 @@
-# Default ignored files
-/shelf/
-/workspace.xml
-# Editor-based HTTP Client requests
-/httpRequests/
-# Datasource local storage ignored files
-/dataSources/
-/dataSources.local.xml
-# Zeppelin ignored files
-/ZeppelinRemoteNotebooks/

CHANGELOG.md

@@ -1,3 +1,9 @@
+## v0.1.2 (2025-11-08)
+
+### Refactor
+
+- Gave the GitHub MCP server a default placeholder value that doesn't require the vault
+
 ## v0.1.1 (2025-11-08)
 
 ## v0.1.0 (2025-11-07)

Cargo.lock

@@ -3089,7 +3089,7 @@ dependencies = [
 
 [[package]]
 name = "loki-ai"
-version = "0.1.1"
+version = "0.1.2"
 dependencies = [
  "ansi_colours",
  "anyhow",

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "loki-ai"
-version = "0.1.1"
+version = "0.1.2"
 edition = "2024"
 authors = ["Alex Clarke <alex.j.tusa@gmail.com>"]
 description = "An all-in-one, batteries included LLM CLI Tool"

README.md

@@ -164,21 +164,6 @@ guide you through the process when you first attempt to access the vault. So, to
 loki --list-secrets
 ```
 
-### First Time Setup
-In order for Loki to function correctly, you'll need to add a few secrets to the Loki vault so the MCP servers can
-function.
-
-**GitHub MCP Server:**
-* `GITHUB_PERSONAL_ACCESS_TOKEN` - A GitHub Personal Access Token with `repo` and `workflow` scopes.
-  See [Creating a GitHub Personal Access Token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)
-
-#### Add the secrets to the Loki vault
-You can add the secrets to the Loki vault using the following commands (First time use will prompt you to create a vault 
-password file):
-```sh
-loki --add-secret GITHUB_PERSONAL_ACCESS_TOKEN
-```
-
 ### Tab-Completions
 You can also enable tab completions to make using Loki easier. To do so, add the following to your shell profile:
 ```shell

assets/functions/mcp.json

@@ -11,21 +11,12 @@
         "ghcr.io/github/github-mcp-server"
       ],
       "env": {
-        "GITHUB_PERSONAL_ACCESS_TOKEN": "{{GITHUB_PERSONAL_ACCESS_TOKEN}}"
+        "GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_TOKEN"
       }
     },
     "docker": {
       "command": "uvx",
       "args": ["mcp-server-docker"]
-    },
-    "slack": {
-      "command": "npx",
-      "args": ["-y", "slack-mcp-server@latest", "--transport", "stdio"],
-      "env": {
-        "SLACK_MCP_XOXC_TOKEN": "{{SLACK_MCP_XOXC_TOKEN}}",
-        "SLACK_MCP_XOXD_TOKEN": "{{SLACK_MCP_XOXD_TOKEN}}",
-        "SLACK_MCP_ADD_MESSAGE_TOOL": true
-      }
     }
   }
 }

docs/AICHAT-MIGRATION.md

@@ -3,8 +3,8 @@ Loki originally started as a fork of AIChat but has since evolved into its own s
 
 As a result, there's some changes you'll need to make to your AIChat configuration to be able to use Loki.
 
-Be sure you've followed the [first-time setup steps](../README.md#first-time-setup) so that the Loki configuration 
-directory and subdirectories exist and is populated with the built-in defaults.
+Be sure you've run `loki` at least once so that the Loki configuration directory and subdirectories exist and is
+populated with the built-in defaults.
 
 ## Global Configuration File
 You should be able to copy/paste your AIChat configuration file into your Loki configuration directory. Since the