Is There a Roadmap for Future Corsair Development?

No, Corsair does not maintain a static roadmap document; instead, future development is tracked through GitHub issues labeled "roadmap," community Discord discussions, and integration tags in the codebase.

Corsair is an open-source integration platform whose direction is driven by community contributions rather than top-down planning. The corsairdev/corsair repository uses a dynamic, living approach to planning that reflects the realities of distributed open-source development. This article explains exactly where roadmap information lives in the codebase and how to access it programmatically.

How Corsair Tracks Future Development

Unlike traditional software projects with fixed roadmaps, Corsair distributes planning information across three interconnected systems. Understanding each helps you stay current with actual priorities rather than outdated documents.

GitHub Issues and Pull Requests

The primary venue for feature planning is the GitHub issue tracker. Maintainers use the "roadmap" label to classify issues representing planned work.

To find current roadmap items:

# Filter open issues by the roadmap label

# https://github.com/corsairdev/corsair/issues?q=label%3Aroadmap+is%3Aopen

You can also monitor open pull requests for work-in-progress features. The repository's CONTRIBUTING.md explicitly directs contributors to discuss significant changes via issues before submitting code.

Discord Community Server

The project maintains an official Discord server at https://discord.gg/uNgCP3mSzU. This is where maintainers:

• Announce upcoming priorities
• Gather community feedback on proposed features
• Coordinate release timing

For real-time roadmap awareness, joining this server is more valuable than any static document.

OSS Integrations Page

The hosted page at https://corsair.dev/oss serves as a visual registry of integrations. When contributors want to add new integrations, they claim them here. The page indirectly reveals roadmap priorities by showing:

• Completed integrations — already implemented
• Claimed integrations — actively in development
• Unclaimed integrations — opportunities for contribution

The "Roadmap" Tag in the Codebase

Corsair implements a formal tagging system for integrations. The roadmap tag is defined programmatically and applied to integrations that align with the project's longer-term vision.

Tag Definition Location

In www/src/db/integration-tag-definitions.ts, the roadmap tag is identified by this regular expression:

// From www/src/db/integration-tag-definitions.ts
const tagPatterns = {
  // ... other tags
  roadmap: /kanban|sprint|backlog|roadmap/i,
};

This pattern matches multiple planning-related terms, ensuring broad categorization of future-oriented work.

Querying Roadmap Integrations Programmatically

You can extract current roadmap items directly from the database layer:

// List all integrations tagged as "roadmap"
import { getIntegrations } from '@/www/src/db/integrations';
import { ROADMAP_TAG } from '@/www/src/db/integration-tag-definitions';

const roadmapIntegrations = await getIntegrations()
  .filter(i => i.tags.includes(ROADMAP_TAG));

console.log('Planned (roadmap) integrations:', 
  roadmapIntegrations.map(i => i.name));

Integrations carrying this tag receive special UI treatment. The www/src/components/landing/problem-statement/problem-statement-section.tsx component renders these as "roadmap" items, signaling to users that these features are planned or in-progress.

Command-Line Discovery via Corsair CLI

The explorer/src/cli.ts module provides built-in CLI capabilities for querying integration status, including roadmap filtering.

List Roadmap Integrations from Terminal

# Query integrations with the roadmap tag

$ npx corsair explorer --list --tag roadmap

# Example output:

#   - Notion (Q4 roadmap)

#   - Google Maps (roadmap)

This command interfaces directly with the same tag definitions used by the web application, ensuring consistent results across interfaces.

Programmatic Access to GitHub Roadmap Issues

For automated monitoring or CI/CD integration, fetch open roadmap issues via the GitHub API:

// Fetch open GitHub issues labeled "roadmap"
import { Octokit } from '@octokit/rest';

const octokit = new Octokit();
const { data: roadmapIssues } = await octokit.issues.listForRepo({
  owner: 'corsairdev',
  repo: 'corsair',
  labels: 'roadmap',
  state: 'open',
});

console.log('Open roadmap issues:', 
  roadmapIssues.map(i => i.title));

This approach is particularly useful for building dashboards or notification systems that track Corsair's evolving priorities.

Key Files for Roadmap Investigation

File Path	Purpose
README.md	Entry point explaining contribution workflow and OSS integrations page
CONTRIBUTING.md	Guidelines for proposing features and participating in roadmap discussions
www/src/db/integration-tag-definitions.ts	Source of truth for the "roadmap" tag regex and classification logic
www/src/db/integrations.ts	Database layer for querying integration metadata
www/src/components/landing/problem-statement/problem-statement-section.tsx	UI component rendering roadmap status to end users
explorer/src/cli.ts	Command-line interface for integration discovery

Summary

• Corsair has no static roadmap document — planning is distributed across issues, Discord, and code-level tags
• The "roadmap" label on GitHub issues tracks planned features and enhancements
• Integration tags in www/src/db/integration-tag-definitions.ts programmatically identify roadmap items
• Discord at https://discord.gg/uNgCP3mSzU is the primary real-time communication channel for future plans
• CLI and API methods enable programmatic monitoring of roadmap status

Frequently Asked Questions

How do I find what features are planned for Corsair?

Check the GitHub issues filtered by the "roadmap" label, join the Discord server, or query integrations tagged as roadmap using the CLI command npx corsair explorer --list --tag roadmap. The OSS integrations page at https://corsair.dev/oss also shows claimed and unclaimed integrations indicating near-term priorities.

Can I propose a new feature or integration for the roadmap?

Yes. According to CONTRIBUTING.md, open a GitHub issue describing your proposal, discuss it in the Discord server, and for integrations, claim it on the OSS integrations page. Features that align with community needs and maintainers' vision receive the roadmap tag.

Is the roadmap tag applied automatically or manually?

Manually. The ROADMAP_TAG constant in www/src/db/integration-tag-definitions.ts provides the classification mechanism, but maintainers apply it to specific integrations based on strategic priority and community demand.

How can I get notified when the roadmap changes?

Watch the corsairdev/corsair repository on GitHub for issue and PR activity, join the Discord server for announcements, or implement the Octokit-based code example above to poll for new roadmap-labeled issues programmatically.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}