Arco

Product Introduction

1. Definition: Arco is a free, open-source, MIT-licensed Model Context Protocol (MCP) server and plugin designed for the Codex desktop environment. It functions as a local issue management bridge, enabling direct interaction with GitHub and Linear APIs from within an AI chat interface.
2. Core Value Proposition: Arco exists to eliminate context switching for developers and project managers by integrating issue tracking directly into their AI-assisted workflow. Its primary value is providing a local, secure, and unified workspace to view, edit, and contextualize issues from GitHub and Linear without leaving the Codex application, thereby enhancing productivity and focus.

Main Features

1. Multi-Provider Issue Management: Arco provides a unified interface for two major platforms. For GitHub, it leverages the official gh CLI for authentication, utilizing existing tokens and permissions. For Linear, it implements a full OAuth 2.0 flow, storing refresh tokens securely in the operating system's native credential store (e.g., macOS Keychain, Windows Credential Manager, Linux Secret Service). This allows users to independently connect to and manage issues from either service.
2. Contextual Issue Workspace: The plugin offers three viewing modes: inline cards within the chat, a dedicated side panel, and a full-screen view. This multi-pane approach allows for comparing issues in-conversation while having detailed views readily accessible. The interface renders native issue fields, Markdown descriptions, comments, and metadata (labels, status, assignees) fetched directly from the provider's API.
3. Seamless Context Integration into AI Prompts: A core technical feature is the ability to select specific text passages from any open issue (across GitHub or Linear) and collect them as numbered excerpts. These excerpts are then automatically appended as context to the user's next prompt sent to the AI model within Codex, enabling highly informed and precise AI interactions based on real project data.
4. Local-First Architecture & Security: Arco operates as a local Node.js server (requiring Node 24.22.1+). All data processing and API calls occur directly from the user's machine. There is no Arco backend server, meaning issue data, credentials (managed via OS keyring and gh CLI), and API keys never leave the user's local environment, addressing critical data privacy and security concerns.

Problems Solved

1. Pain Point: Constant context switching between an AI coding assistant (like Codex), a browser-based issue tracker (GitHub/Linear), and the development environment fragments focus and disrupts workflow.
2. Target Audience: The primary user personas are Software Developers and Technical Project Managers/Team Leads who use Codex for AI-assisted development and rely on GitHub Issues, GitHub Projects, or Linear for task tracking and sprint planning. It is especially valuable for developers managing their assigned tickets or project leads triaging incoming reports.
3. Use Cases:
   • AI-Powered Issue Triage: A developer can ask Codex to summarize a batch of newly assigned GitHub issues, then use Arco to view details, update statuses, and add comments without switching tabs.
   • Context-Aware Code Generation: A developer can select error descriptions and reproduction steps from a Linear bug report, feed them directly into Codex as context, and generate a targeted fix.
   • Meeting Preparation & Updates: A project manager can review "In Progress" items from both GitHub and Linear in the side panel, compile status updates, and draft sprint summaries within the same window used for communication.

Unique Advantages

1. Strengths & Limitations (Pros & Cons):

   • Pros:
     • Zero-Cost & Open Source: Free MIT license allows for inspection, modification, and community contribution.
     • Superior Privacy: Local execution ensures sensitive issue data and project details are not transmitted to third-party servers.
     • Deep Workflow Integration: The "select-to-context" feature is a unique differentiator that tightly couples issue management with AI assistance.
     • Native Provider Experience: Preserves the specific fields and workflows of both GitHub and Linear without imposing a lowest-common-denominator schema.
   • Cons:
     • Platform & Setup Complexity: Requires specific, recent versions of Node.js, the codex CLI, and (for GitHub) the gh CLI. Source builds are platform-specific.
     • Limited Provider Ecosystem: Currently only supports GitHub and Linear. Integrations with Jira, Asana, or others are absent.
     • Dependency on Codex Ecosystem: Exclusively a Codex plugin, offering no value for users of Cursor, Windsurf, or other AI-IDEs.
     • Manual Update Process: Updates require CLI commands (codex plugin add...) and a Codex restart, lacking an automatic update mechanism.

2. Key Alternatives & Differentiation:

   • Browser Tabs / Native Apps: The traditional method. Arco differentiates by centralizing the workflow inside the AI tool, eliminating tab sprawl and enabling direct context sharing with the AI model, which browsers cannot do.
   • Zapier / Make (Integromat): These are cloud-based automation platforms that can connect GitHub/Linear to other apps. Arco differentiates by being local, privacy-focused, and offering real-time interactive editing and context selection within the developer's primary interface, rather than being a background automation tool.
   • Other MCP Servers (e.g., for Google Calendar, Filesystem): While other MCP servers exist, Arco is specifically tailored and optimized for the bi-directional interaction with issue trackers, offering a rich UI component and edit capabilities beyond simple read-only data fetching.

Frequently Asked Questions (FAQ)

1. Is Arco secure for my private company issues? Yes. Arco's security model is a key advantage. It runs locally on your machine, uses your existing gh CLI auth for GitHub, and stores Linear tokens in your OS's encrypted credential store. Your issue data is never sent to an Arco-controlled server.
2. Can I use Arco with Cursor or VS Code? No. Arco is built specifically as a plugin for the Codex desktop environment and utilizes its proprietary plugin and interactive UI framework. It is not compatible with Cursor, VS Code, or other code editors.
3. Does Arco sync data between GitHub and Linear? No. Arco is a unified viewer and editor, not a synchronization tool. It presents issues from each provider in their native format and allows edits, but it does not create copies or keep records in sync between GitHub and Linear. Each service remains the single source of truth.
4. What are the system requirements to install Arco? You need the Codex desktop app with local plugin support, the codex CLI, Git, npm, and Node.js 24.22.1 or later. For the prebuilt package, you must be on macOS (Apple Silicon). For GitHub, the official gh CLI must also be installed and authenticated.
5. How do I update the Arco plugin? Updating is a manual process via the command line. For the prebuilt version, run codex plugin marketplace upgrade arco-marketplace followed by codex plugin add arco@arco-marketplace. You must then restart the Codex desktop application for the update to take effect.