Skip to content

Supported Development Environments

FineCode is designed to expose the same actions across the development surfaces teams already use: terminal, editor, CI, git hooks, and AI tooling.

The recommended path today is:

  1. Start with the CLI.
  2. Add the VSCode extension if your team works in VS Code.
  3. Reuse the same actions in CI and git hooks.
  4. Add MCP for AI-assisted workflows when useful.

Support matrix

Environment Status Recommended path Notes
VSCode Supported IDE and MCP Setup Official IDE integration today. Includes LSP features, action sidebar, formatting, diagnostics, testing integration, and Copilot MCP registration through the extension.
Other IDEs and editors Planned / custom integration LSP and MCP Architecture FineCode ships an LSP server, but the only packaged IDE integration documented and tested today is VSCode. For now, other IDE integrations would need to come through LSP-based clients.
CLI Supported Getting Started and CLI Reference Best starting point for local runs, scripts, and debugging.
CI Supported CLI Reference and Multi-Project Workspace Reuse the same run commands in pipelines. FineCode auto-detects CI via the CI environment variable.
Git hooks Supported Using Git Hooks FineCode can install a git pre-commit hook that runs staged-file checks before commit.
AI assistants via MCP Supported IDE and MCP Setup Works with MCP-compatible clients such as Claude Code. In VS Code, the extension-managed path is recommended when available.

CLI

The CLI is the baseline integration and the easiest place to start:

python -m finecode run lint
python -m finecode run format
python -m finecode prepare-envs

Use the CLI when you want a direct local workflow, shell scripting, or a simple building block for CI.

IDE

VSCode is the primary IDE integration today through the FineCode extension.

That path gives you:

  • inline diagnostics
  • formatting and code actions
  • action discovery in the sidebar
  • test discovery and execution
  • automatic MCP registration for VS Code Copilot

If you need another IDE, FineCode already exposes an LSP server, but there is not yet another official packaged integration in the user docs.

CI

CI should reuse the same FineCode actions you run locally instead of duplicating tool-specific wiring:

python -m finecode run --concurrently lint check_formatting

In CI environments, FineCode automatically detects CI=... and marks the run as ci.

Git Hooks

Git hooks are the lightweight enforcement layer before code even reaches CI.

Install the hook with:

python -m finecode run install_git_hooks

The installed hook runs FineCode's precommit action on staged files. You can supply that action through the fine_precommit preset or by declaring your own precommit handlers.

AI Assistants and MCP

FineCode exposes actions through an MCP server, so AI clients can call the same action surface that developers use in the CLI and IDE.

At a minimum, MCP clients launch:

.venvs/dev_workspace/bin/python -m finecode start-mcp

For VS Code users, the extension-managed path is preferred. For other MCP clients, use the client-specific configuration described in IDE and MCP Setup.