OpenCode vs TabnineUpdated 2026-03-16

SUMMARY

OpenCode (CLI) uses markdown configuration while Tabnine (IDE) uses markdown. They differ on 4 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

FeatureOpenCodeTabnine
Config formatmarkdownmarkdown
Hierarchy support
Global config
Project config
Subdirectory scoping
File inclusion / imports
Ignore file
IDE integrationCLI
Schema / structureFree-form (Markdown)Free-form (Markdown)
Git committed
EncodingUTF-8UTF-8

FILE MAPPING

PurposeOpenCodeTabnine
Project instructionsAGENTS.md.tabnine/guidelines/*.md
Settings / configurationopencode.json.tabnine/agent/commands/

SIDE-BY-SIDE CODE SAMPLES

OpenCode
AGENTS.md
markdown
# Project Instructions

## Overview
This is a TypeScript monorepo using pnpm workspaces.

## Code Style
- Use strict TypeScript with no implicit any
- Prefer functional components with hooks
- All exports should be named (no default exports)

## Architecture
- /packages/core — shared business logic
- /packages/ui — React component library
- /apps/web — Next.js frontend

## Build & Test
Run tests with: pnpm test
Build all packages: pnpm build
All PRs must have >80% coverage on changed files.

## Conventions
- Use conventional commits (feat:, fix:, chore:)
- Prefer composition over inheritance
- See @docs/api-guidelines.md for API design patterns

Tabnine
.tabnine/guidelines/*.md
markdown
# Application Guidelines

## Architecture
- This is a monorepo managed with Turborepo
- Apps: web (Next.js), api (Express), mobile (React Native)
- Shared packages: ui, config, types

## Code Standards
- TypeScript strict mode in all packages
- Use barrel exports (index.ts) for public APIs
- No default exports; use named exports everywhere
- Prefer async/await over raw Promises

## API Design
- RESTful endpoints follow /api/v1/{resource} pattern
- All responses use { data, error, meta } envelope
- Validate request bodies with Zod schemas
- Return 4xx for client errors, 5xx for server errors

## Database
- Use Prisma ORM for all database operations
- Migrations checked into source control
- Soft-delete pattern: use deletedAt timestamp, never hard delete
- All timestamps stored as UTC

## Testing
- Jest for unit tests, Playwright for E2E
- Test files colocated: foo.ts -> foo.test.ts
- Mock external services, never call real APIs in tests

KEY DIFFERENCES

1. Hierarchy support

OpenCode: Supported. Tabnine: Not supported.

2. Global config

OpenCode: Supported. Tabnine: Not supported.

3. Subdirectory scoping

OpenCode: Supported. Tabnine: Not supported.

4. IDE integration

OpenCode: CLI. Tabnine: Supported.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use OpenCode, configure AGENTS.md. If you use Tabnine, configure .tabnine/guidelines/*.md. Many projects include config files for multiple tools so each team member can use their preferred editor.

PORTABILITY TIP

sync-instructions.sh
bash
# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md

SEE ALSO

agentconfig.ing2026-03-16COMPARE(1)