Ai

You can build a fully local meeting transcriber on Linux. Capture system audio with PipeWire. Transcribe with Faster-Whisper on your GPU. Pipe the transcript to a local LLM through Ollama for structured summaries with names, decisions, and action items. The pipeline runs on 16GB of RAM and a mid-range NVIDIA GPU, and produces notes within seconds of the call ending. No data leaves your network.

Commercial services like Otter.ai and Fireflies.ai route your audio through their servers. If your meetings cover sensitive topics like product plans, HR, or legal reviews, that’s a non-starter. A local pipeline gives you the same structured output, and nothing leaves your building.

You can unify access to Ollama, vLLM, cloud providers like OpenAI, Anthropic, and Google, plus custom model servers behind one OpenAI-compatible endpoint using LiteLLM Proxy . LiteLLM is a reverse proxy. It maps the standard /v1/chat/completions request to each provider’s native API. From one YAML file it handles auth, model routing, load balancing, fallbacks, rate limits, and spend tracking. Your app calls one endpoint with one key, and LiteLLM picks the right backend. You can swap models, add providers, or run A/B tests without touching app code.

Three focused AI coding agents beat one broad agent working three times as long. Addy Osmani showed this at O’Reilly AI CodeCon , and the finding captures both the upside and the catch of multi-agent work. The speed gains are real. They only show up when you solve the coordination problem. Without file isolation, iteration caps, and review gates, parallel agents make a mess of merge conflicts and duplicated work.

Claude Code, Cursor, and GitHub Copilot take three very different shots at AI-assisted coding: a terminal-native agent, an AI-first IDE, and a multi-IDE plugin. Claude Code leads on raw skill and complex multi-file work, scoring highest on SWE-bench at about 74-81%. Cursor offers the best editor experience with background agents and cloud automation. GitHub Copilot has the lowest entry price at $10/month and the widest IDE support. Most pro developers now mix two or more tools, with Claude Code plus Cursor as the top pair per the JetBrains AI Pulse survey from January 2026.

Git worktrees let you attach many working directories to a single repo. Each one has its own branch checked out. Claude Code ships a native --worktree (-w) flag that handles the setup in one command. It creates a worktree, checks out a new branch, and launches Claude inside it. Run the same command in another terminal and you’ve got a second agent. Scale to five, ten, or more sessions and none of them clash on disk.

I get better output from Claude Code by adding fewer tools, not more. Piling on MCP servers rarely helps, but the right official marketplace plugins, CLI tools, and skills do. Start with /plugin and picks like typescript-lsp and security-guidance, then add Supabase CLI, Playwright, GitHub CLI, and the GSD framework. That stack handles code, deploys, research, and browser work on its own.

When I first found Claude Code, I tried to connect every MCP server I could find. Within a week, the agent felt slower and less decisive, and it often picked the wrong tool for the job. The fix was almost always a smaller, more careful toolset.