GitHub Copilot vs Goose | agentconfig.ing

GitHub Copilot vs GooseComparisonUpdated 2026-03-16

SUMMARY

GitHub Copilot (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	GitHub Copilot	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	GitHub Copilot	Goose
Project instructions	.github/copilot-instructions.md	.goosehints
Project instructions	.github/instructions/*.instructions.md	AGENTS.md

SIDE-BY-SIDE CODE SAMPLES

GitHub Copilot

.github/copilot-instructions.md

markdown

# Copilot Instructions

## Code Style
- Use TypeScript strict mode for all new files
- Prefer functional components with hooks over class components
- Use named exports, not default exports

## Libraries
- Use date-fns for date manipulation (not moment.js)
- Use zod for runtime validation
- Prefer fetch over axios for HTTP requests

## Testing
- Write tests using Vitest
- Use Testing Library for component tests
- Aim for integration tests over unit tests

## Conventions
- Use camelCase for variables, PascalCase for components
- Prefix interfaces with I (e.g., IUserProps)
- Keep files under 300 lines; extract if longer

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

GitHub Copilot: markdown. Goose: text.

2. Global config

GitHub Copilot: Not supported. Goose: Supported.

3. Subdirectory scoping

GitHub Copilot: Supported. Goose: Not supported.

4. IDE integration

GitHub Copilot: Supported. Goose: CLI.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use GitHub Copilot, configure .github/copilot-instructions.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