bguiz

How to configure kimi-cli to use Kimi 2.5 via OpenRouter

(1) Install kimi-cli:

• https://kimi.com/code
• curl -L code.kimi.com/install.sh | bash

(2) Edit/ replace ~/.kimi/config.toml with the provided config.toml file.

• type needs to be openai_legacy, not openai
• base_url must include the /api/v1 path
• model must be moonshotai/kimi-k2.5 (note the additional k)

bguiz

#!/usr/bin/env node

import fs from 'node:fs/promises';

// extract inputs
const OPENROUTER_API_KEY = process.env.OPENROUTER_API_KEY;
const IMAGE_NAME = process.env.IMAGE_NAME;
const AI_MODEL = process.env.AI_MODEL || 'google/gemini-3-pro-image-preview';
const ASPECT_RATIO = process.env.ASPECT_RATIO || '1:1';
const IMAGE_SIZE = process.env.IMAGE_SIZE || '1K';

bguiz

Status: WIP

Install software via brew

mkdir -p ~/code/
cd ~/code/

# Install brew itself
curl -fsSL "https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh" > brew-install.sh

bguiz

#!/usr/bin/env node

const fs = require('node:fs/promises');
const path = require('node:path');
const gitbookParsers = require('gitbook-parsers');

const SUMMARY_PATH = '../.gitbook/SUMMARY.md';
const DOCS_JSON_PATH = '../.gitbook/docs.json';
const MV_COMMANDS_PATH = '../scripts/mv-commands.sh';

bguiz

name: Technical Writer user
description: A technical writer with several years experience documenting and simplifying complex concepts for developers and users in the blockchain and crypto space, information architecture, maintaining developer portals and managing documentation projects looking to understand user journeys and content developers and stakeholders need to build dApps and gain product knowledge.
expertise:
  technical: High
  domain: High (in their content and technical writing, documentation area)
  tools: Familiarity with git, command line,information architecture, markdown and content writing, documentation
background:
  education: Bachelors degree or equivalent
  experience: Several years in technical writing, documentation, user research and managing docs projects, limited technical experience
traits:

bguiz

flowchart TD
    %% style
    classDef n fill:#3d3,stroke:#111,stroke-width:2px,font-size:56px;
    linkStyle default stroke-width:2px;

    %% touch points
    tpx_google:::n@{ shape: rounded, label: "Google" }
    tpi_site:::n@{ shape: rounded, label: "Inj site" }
    tpi_site_build:::n@{ shape: rounded, label: "Inj site build page" }
    tpi_summit_site:::n@{ shape: rounded, label: "Inj Summit site" }

bguiz

#!/usr/bin/env node
import { ToolNode } from '@langchain/langgraph/prebuilt';
import {
  StateGraph,
  MessagesAnnotation,
  MemorySaver,
  START,
  END,
  interrupt,
  Command,

bguiz

bguiz

#!/bin/zsh

##
## This automation was created to be used with MACOS based on the instructions from drduh
## (https://github.com/drduh/YubiKey-Guide)
##
## You need to install gpg first:
## brew install gnupg hopenpgp-tools ykman pinentry-mac
## and GPG Suite can also come in handy (https://gpgtools.org/)
##

bguiz

// web3 provider with fallback for old version

window.addEventListener('load', async () => {
    // New web3 provider
    if (window.ethereum) {
        window.web3 = new Web3(ethereum);
        try {
            // ask user for permission
            await ethereum.enable();
            // user approved permission