breaked
0 Followers · 0 Following
  • Joined on 2025-08-22
Repositories
1
 Projects Packages Public Activity Starred Repositories

@octo/env-setup (1.1.0)

Published 2026-03-03 13:11:13 +03:00 by breaked

Installation

@octo:registry=
npm install @octo/env-setup@1.1.0
"@octo/env-setup": "1.1.0"

About this package

octo-env-setup

Installer for the Octo AI toolchain.

Components

  • grepai — Semantic code search
  • octo-mcp-thin — MCP proxy (Semantic + Regex + Web + Fetch)
  • fantazzy-mcp — Persistent memory MCP server
  • octo-skills — AI skills manager
  • agents-tuning-light — System prompt builder from partials

Prerequisites

  • grepai — curl -sSL https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.sh | sh
  • node >= 18, npm
  • php >= 8.2, composer (for laravel-mcp-thin)
  • rg (ripgrep) — recommended for regex search
  • SSH access to gitea.breaked.me and git.ropos.cloud (the installer clones private repos)
  • OpenAI API key for embeddings (optional: can use ollama/lmstudio instead)
  • Fantazzy API key (prompted interactively if not passed via --fantazzy-key)

Installation

One-time setup (per machine)

Configure npm to use the Gitea registry for @octo packages:

npm config set @octo:registry https://gitea.breaked.me/api/packages/breaked/npm/
npm config set //gitea.breaked.me/api/packages/breaked/npm/:_authToken YOUR_GITEA_TOKEN

Then install globally:

npm install -g @octo/env-setup

Alternative: install from git

git clone git@gitea.breaked.me:breaked/octo-setup-env.git /tmp/octo-setup-env
cd /tmp/octo-setup-env
npm install && npm run build && npm link

Usage

octo-setup-env [project-path] [options]

Options

Flag Description Default
--dir <path> Target directory for tools .ai-tools
--embedder <provider> grepai embedder: openai, ollama, lmstudio openai
--openai-key <key> OpenAI API key for embeddings —
--targets <list> MCP config targets: claude, roo, gemini, codex, all all
--fantazzy-url <url> Fantazzy API URL http://localhost:5000
--fantazzy-key <key> Fantazzy API key —
--submodule Use git submodules instead of standalone clones —
--force Overwrite existing installations —
--skip <component> Skip components: grepai, mcp, fantazzy, skills —
--json Output setup report as JSON —

Example

octo-setup-env /data/web/my-project --openai-key sk-... --targets claude,roo

What happens

  1. Checks prerequisites (grepai, php, node, rg)
  2. Creates .ai-tools/ directory
  3. Prompts for Fantazzy API key and OpenAI key (if not passed via CLI flags)
  4. Clones and installs: laravel-mcp-thin, octo-mcp-thin, fantazzy-mcp, octo-skills, agents-tuning-light
  5. Initializes grepai with config
  6. Analyzes project structure (stack, directories, file counts)
  7. Generates MCP configs (.mcp.json, .roo/mcp.json)
  8. Creates systemd service template for grepai watch
  9. Saves setup report to .ai-tools/setup-report.json

After installation

Run the env-setup-review skill (available in Claude Code, Roo Code, etc.) to:

  • Review and fine-tune grepai ignore/boost config
  • Validate MCP server connectivity
  • Optimize settings for your specific project stack

To build agent system prompts for the project:

cd .ai-tools/agents-tuning-light && node build.js -r /path/to/project

Publishing (maintainer)

npm run build
npm publish

The publishConfig in package.json points to the Gitea npm registry automatically.

Dependencies

Dependencies

ID Version
chalk ^5.6.2
commander ^14.0.3
fs-extra ^11.3.3
inquirer ^13.3.0

Development Dependencies

ID Version
@types/fs-extra ^11.0.4
@types/inquirer ^9.0.9
@types/node ^25.3.1
ts-node ^10.9.2
typescript ^5.9.3

Keywords

ai toolchain mcp grepai setup
Details
npm
2026-03-03 13:11:13 +03:00
2
breaked
ISC
latest
7.2 KiB
Assets (1)
env-setup-1.1.0.tgz 7.2 KiB
Versions (2) View all
1.1.0 2026-03-03
1.0.1 2026-03-03