Gemini Code Assist vs Goose

Gemini Code Assist vs GooseComparisonUpdated 2026-03-18

SUMMARY

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

FEATURE COMPARISON

Feature	Gemini Code Assist	Goose	Notes
Config format	markdown	text
Hierarchy support	✓	✓	Whether config files can be placed at multiple directory levels
Global config	✗	✓	User-wide configuration outside any project
Project config	✓	✓
Subdirectory scoping	✓	✗	Config files in subdirectories that apply only to that subtree
File inclusion / imports	✗	✗	Ability to include or reference other files from config
Ignore file	✗	✗
IDE integration	✓	CLI
Schema / structure	Free-form (Markdown)	Free-form (Markdown)	Whether config uses structured schema or free-form content
Git committed	✓	✓	Whether primary config files are intended to be version-controlled
Encoding	UTF-8	UTF-8

FILE MAPPING

Purpose	Gemini Code Assist	Goose
Project instructions	GEMINI.md	.goosehints
Project instructions	AGENT.md	AGENTS.md

SIDE-BY-SIDE CODE SAMPLES

Gemini Code Assist

GEMINI.md

markdown

# Project Rules

## Overview
E-commerce platform built with Go microservices and React frontend.
All services communicate via gRPC with Protocol Buffers.

## Go Services
- Follow standard Go project layout (cmd/, internal/, pkg/)
- Use structured logging with slog (not log or fmt.Println)
- Error handling: always wrap errors with fmt.Errorf("%w", err)
- Database access through repository pattern in internal/repo/
- All public functions must have godoc comments

## API Design
- Proto files live in proto/ directory with buf for linting
- Use field masks for partial updates
- Pagination via cursor-based tokens, not offset

## Testing
- Table-driven tests for all business logic
- Use testcontainers-go for integration tests
- Minimum 80% coverage on internal/ packages
- Mock external services with gomock interfaces

## Do Not
- Use global variables or init() functions
- Import internal packages across service boundaries
- Commit generated .pb.go files (CI generates them)

Goose

.goosehints

text

This is a Ruby on Rails 7.2 application with Hotwire/Turbo.

Database: PostgreSQL 16
Ruby version: 3.3.x
Node: 22.x (for asset pipeline)

Key commands:
- bin/rails server — start dev server
- bin/rails test — run test suite
- bin/rails db:migrate — run migrations

Conventions:
- Use ViewComponents for reusable UI
- Stimulus controllers for JS behavior
- System tests with Capybara + Playwright
- RuboCop for linting (run: bundle exec rubocop)

KEY DIFFERENCES

1. Config format

Gemini Code Assist: markdown. Goose: text.

2. Global config

Gemini Code Assist: Not supported. Goose: Supported.

3. Subdirectory scoping

Gemini Code Assist: Supported. Goose: Not supported.

4. IDE integration

Gemini Code Assist: Supported. Goose: CLI.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Gemini Code Assist, configure GEMINI.md. If you use Goose, configure config.yaml. 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