Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Threadline — Codex & ClaudeNew to Visual Studio Code? Get it now.
Threadline — Codex & Claude

Threadline — Codex & Claude

Preview

ANTRAZAL

|
3 installs
| (1) | Free
Codex and Claude threads across accounts. Manual tags, drag-and-drop groups, priorities, usage, and parallel editor tabs.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Threadline — Codex & Claude

Keep your coding-agent conversations organized, across projects and accounts, inside VS Code.

Find a thread as you type. Add manual tags, group related work, set priorities, and open conversations beside your files.

One place for your threads

  • Codex and Claude together. Provider icons make each conversation easy to recognize.
  • Projects, tags, and groups. Tag a project to include all its threads, or organize individual conversations. Drag one or several threads onto a tag, group, or priority.
  • Search that stays visible. Results update on every keystroke. Sort by created date, last-used date, or priority.
  • Parallel editor tabs. Resume a thread in the main editor, open it beside another, or select up to four threads to open side by side.
  • Multiple accounts. Choose the account for your next new or reopened conversation. The selected account is underlined.
  • Usage at a glance. See percentage remaining, reset dates, and countdowns in a compact account line. Account details show the available quota windows.
  • A manageable list. Pin, rename, preview, and archive conversations locally. Restore archived threads whenever you need them.

Tags are manual. Dragging to a tag adds that tag; dragging to a group changes the group. Organization changes do not move project files or merge conversation messages.

Get started

  1. Install Threadline in desktop VS Code 1.96 or later.
  2. Install and sign in to Codex, Claude Code, or both using their own extension or CLI.
  3. Click the ANTRAZAL A in the activity bar. Open the dashboard with ⌘⌥T on macOS or Ctrl+Alt+T on Windows/Linux.
  4. Search for a conversation and click it to resume. Use Open beside to keep another thread visible.
  5. Create a tag or group with +, then drag threads into it.

For a downloaded preview package, run Extensions: Install from VSIX… and select the supplied .vsix file.

Release status: tested on macOS. Windows, Linux, SSH, WSL, and development-container workflows have not yet completed release verification. Native editor integration depends on the installed provider version; see the compatibility notes below.

Accounts and usage

Your default local agent homes appear automatically. Add account creates a separate home and opens the provider's sign-in. Connect existing registers a home you already use. Existing profiles from Codex Switch and Codex Accounts Manager can also be discovered; Threadline delegates their switching and reauthentication to the original manager.

The compact account line stays available in the dashboard, sidebar, and status bar. Click an account to select it. Accounts shows more detail and recovery controls.

Indicator Meaning
Green A recent live usage check succeeded. This does not prove an already-open native editor has refreshed its credentials.
Neutral Saved usage, a pending check, or sign-in in progress. Cached usage is labeled.
Red An authentication failure was confirmed. Use Reauthenticate for that account.
Amber Usage needs attention, or the native Codex editor needs a reload. Use the action shown.

Usage refreshes automatically in trusted workspaces. Expired readings are not presented as current quota. Availability depends on the provider, plan, authentication, and installed client; API-key accounts may not expose subscription limits. Usage checks do not submit a coding task.

Complete one sign-in per provider at a time. Finish sign-in opens VS Code Notifications, where the existing account-manager login can be cancelled. Closing its browser tab alone does not cancel it. After credentials change, Reload Codex reloads this VS Code window so the native editor uses the new sign-in. Reloading can interrupt running work in that window.

Selecting another account affects the next new or reopened thread. Already-running sessions keep their process context. A provider's shared native sign-in follows that provider's switching behavior; isolated account homes use separate editor terminals.

Opening conversations

In Auto mode, Threadline uses the installed provider's native editor when its account and project context match. Isolated profiles use editor terminals. Claude threads from another project resume their saved transcript in an editor terminal in the current window.

Native conversation routing uses provider commands and editor contracts that may change between versions. If an update breaks native opening, set Threadline: Open Mode to terminal. Providers still control their own permissions, authentication, session locks, and execution.

Open now means an identifiable conversation tab is open; it is not a live activity monitor. Multiple threads in the same project share that project's files.

History and settings

Threadline reads local Codex history from $CODEX_HOME or ~/.codex, and Claude history from $CLAUDE_CONFIG_DIR or ~/.claude. Cloud-only conversations must first be available locally. Older histories may not record which account owned each thread; those limitations are shown rather than guessed.

Modern Codex SQLite history requires built-in Node SQLite support or the system sqlite3 executable. If neither is available, file-based history remains available and Threadline reports the missing source.

Search Threadline in VS Code Settings:

Setting Default Purpose
threadline.groupBy project Group by project, tag, group, priority, account, or none
threadline.openMode auto Prefer native editors, or always use editor terminals
threadline.codexHome / threadline.claudeHome Auto Override the agent's data directory
threadline.codexExecutable / threadline.claudeExecutable Auto Override the provider executable
threadline.refreshInterval 30 Local history refresh interval in seconds
threadline.maxThreads 500 Maximum recent parent threads to index

Executable settings accept a file path or executable name, without additional arguments. Remote workspaces use the workspace host's data and executables. Untrusted workspaces allow history browsing and organization; starting agents and checking live usage require trust.

Privacy and support

Threadline stores organization and account display data in VS Code's local extension storage. It has no Threadline telemetry or analytics endpoint and does not upload your conversation catalog to ANTRAZAL. Provider clients can contact their own services for authentication, usage, and agent work.

Read the privacy notice, troubleshooting and support guide, and changelog.

Threadline is an independent utility by ANTRAZAL, not an official OpenAI or Anthropic extension. Provider names and icons identify their respective products. Threadline is MIT licensed.

Privacy notice

Effective 16 November 2026.

Threadline organizes local Codex and Claude Code conversations inside VS Code. This notice describes Threadline's behavior; the installed providers, account managers, VS Code, and any remote workspace hosts have their own data handling.

Data read locally

Threadline reads the agent homes you use or explicitly register. That can include conversation identifiers, titles, project paths, timestamps, account ownership hints, and transcript text for search and previews. It reads Codex history files and SQLite catalogs and Claude project histories.

For account identity, Threadline may read Codex's local auth.json and decode email/account claims from its ID token. These claims are display and ownership hints, not proof of a valid sign-in. It also reads provider configuration, usage caches, and public metadata from supported account-manager extensions. It does not read those account managers' SecretStorage records.

Data stored by Threadline

VS Code extension storage holds manual tags, project tags, groups, priorities, display names, pins, local archive choices, registered account paths and labels, selected accounts, and sanitized usage snapshots. Usage snapshots can include an account identity, plan, percentages, reset times, check times, and diagnostic reasons. Webview state preserves interface choices such as search and filters.

Threadline does not copy provider tokens into its account registrations or usage cache. When you add an account, it creates a separate agent home under its extension storage; the provider's sign-in process can store its own credentials there or in the provider's credential store.

A private temporary coordination record prevents overlapping Codex logins. It contains process and attempt metadata, not OAuth codes, states, or tokens. Credential-change detection reads file metadata rather than credential contents.

Network and provider activity

Threadline has no analytics, advertising, or Threadline telemetry endpoint. It does not send your conversation catalog to ANTRAZAL.

This does not make every operation offline. In trusted workspaces, Threadline automatically launches bounded account/usage checks through installed provider clients and may ask a supported account manager to refresh saved-account quotas. Those clients can contact their provider services using their existing authentication. Usage checks do not submit a coding task; the supported Claude usage path is checked for a local-command contract and zero model turns/cost.

When you open or resume a conversation, the provider controls any subsequent network requests, model execution, file access, approvals, and charges. Sign-in can open the provider's browser flow. Account switching can ask the original account manager to update the shared provider authentication.

Threadline's webviews load packaged assets and use a restrictive content security policy. They do not load third-party analytics scripts.

Storage location and removal

Storage belongs to the VS Code profile and extension host running Threadline. For remote workspaces, that host may be a remote machine or container rather than your desktop. Normal operating-system, VS Code, workspace-host, and backup access controls apply.

Removing a registered profile from Threadline removes its registration. It does not delete the provider home, credentials, or conversations. Local archive and rename actions affect Threadline's organization; they do not rewrite the provider's conversation history. Use the provider's controls to manage its own credentials and history.

Usage readings expire for display, but an old snapshot can remain in extension storage until replaced or the storage is removed. Uninstalling disables Threadline; VS Code may retain extension data. Threadline does not provide a full-data-erasure command in this release.

Diagnostics and support

Threadline's Output channel can contain diagnostic reasons and local file paths. Screenshots and exported logs may reveal account identities, project names, or conversation content. Review and redact them before sharing. Do not share passwords, API keys, tokens, auth.json, or OAuth callback URLs.

See Support for reporting guidance. Any data you choose to post in a public support channel is visible according to that channel's settings.

Support

After the extension is published, use its Marketplace Q&A to ask questions or report a problem. This release does not yet advertise a separate support site or private security-reporting address.

Quick checks

What you see What to do
A thread is missing Clear filters, check Archive, and refresh. Check the shown/total count and threadline.maxThreads. Cloud-only conversations must be available locally.
No local history is found Check the configured agent home. Remote workspaces read the remote host's files. Codex SQLite catalogs need built-in SQLite support or a system sqlite3 executable.
Native editor opens incorrectly Set Threadline: Open Mode to terminal and try the saved thread again. Report both provider and Threadline versions.
Usage is unavailable Read the account's diagnostic reason and use Retry. Some plans and client versions do not expose subscription quota.
A saved percentage appears but the editor asks for sign-in Saved usage does not verify the editor's credentials. Use Reload Codex after updating the sign-in. If the account reports a confirmed authentication failure, use Reauthenticate.
Sign-in is already pending Use Finish sign-in. Complete the newest browser flow or cancel the account manager's pending login in VS Code Notifications. Closing the browser tab alone does not cancel it. Check the VS Code window where the flow started.
OAuth reports a state mismatch Close the failed callback tab. Finish or cancel the previous pending login, then start one fresh sign-in. Do not reuse the callback URL.
Claude opens a terminal for another project This is expected: native Claude resume is limited to the matching primary workspace project. The saved transcript opens in an editor terminal in the current window.

Reload Codex reloads the current VS Code window and can interrupt work running there. The provider controls authentication, subscription limits, and conversation locks; Threadline cannot bypass them.

Include in a report

  • Threadline version, VS Code version, operating system, and provider extension/CLI versions.
  • Whether the workspace is local, SSH, WSL, or a development container.
  • The action you took, expected result, and actual result.
  • Whether you use a default account, an isolated home, or a supported account manager.
  • A small, redacted screenshot or the relevant lines from View → Output → Threadline, if useful.

Do not post passwords, API keys, tokens, authentication files, OAuth callback URLs, private conversation text, customer data, or unredacted account and project details. Reproductions using synthetic data are preferred.

If you suspect a security problem, keep credentials and exploit details out of public Q&A. Ask the publisher for a private reporting channel before sending sensitive details.

Compatibility status

The current release was verified on macOS with VS Code 1.146.0. Automated tests also cover synthetic histories, account isolation, usage parsing, authentication recovery, and the dashboard/sidebar interface. Windows, Linux, SSH, WSL, and development-container workflows have not yet completed release verification.

Native conversation routing depends on provider commands and editor contracts that can change. Terminal mode remains the recovery option when those native contracts are incompatible. Quota display depends on provider support and a valid account sign-in; test results do not guarantee every provider plan or account configuration.

Release notes

0.3.8 — Preview

  • Prepare the Marketplace description, privacy notice, troubleshooting guide, and sample-data screenshots.
  • Build a preview VSIX from an explicit release file list, excluding internal QA notes, local data, development files, and private repository links.
  • Add a macOS verification workflow and reproducible release packaging. Agent behavior is unchanged from 0.3.7.

0.3.7

  • Keep saved quota neutral; green now means a live usage read, not proof of native editor authentication.
  • Recognize revoked and reused Codex tokens as authentication failures, including failures during the initial account handshake.
  • Reuse pending managed sign-ins and expose Finish sign-in instead of starting another login.
  • Detect same-account credential replacement and offer Reload Codex so the native editor uses the updated sign-in.

0.3.6

  • Check and coordinate the Codex callback port before opening a managed reauthentication flow, preventing a new browser callback from reaching an older login.
  • Reuse pending sign-in terminals and prevent concurrent logins for different accounts of the same provider.
  • Release sign-in coordination when a login completes, fails, closes, or its extension host ends. OAuth state validation remains unchanged.

0.3.5

  • Show green confirmed account health, red authentication failures with a Reauthenticate button, amber refresh problems, and neutral pending checks.
  • Expose distinct authentication, expired-cache, timeout, unsupported-plan, provider and setup issues across the dashboard, sidebar and status bar.
  • Preserve account-specific diagnostics across reloads and clear them after a successful refresh.
  • Route managed-account reauthentication to its original account manager and make Retry refresh saved-account quotas.
  • Align a merged account row’s displayed quota and recovery action with its active registration.

0.3.4

  • Underline the selected account in the compact dashboard and sidebar lines; mark it in the status bar.
  • Identify the weekly reset countdown and date separately from a restrictive short-window reset.
  • Keep native Claude editor support across compatible 2.1 patch updates and always resume the exact transcript for other projects.
  • Detect bundled Claude usage capabilities instead of requiring a hard-coded patch version.

0.3.3

  • Refresh Claude quota through the verified installed 2.1.322 client, including after cached limits expire.
  • Show reset date, month, time, and days/hours/minutes remaining directly in the compact account line.
  • Add account-line navigation arrows so Claude stays reachable in narrow sidebars.
  • Restrict native Claude resumes to their project workspace and resume other-project transcripts in the middle editor; avoid reusing outdated CLI tabs.

0.3.2

  • Open active shared Codex profiles in the native middle editor; recover from older CLI update tabs without killing their processes.
  • Replace pinned account cards with a single line of provider icons, account emails, and percentage left.
  • Match quota to account email and owner, refresh saved accounts through the existing manager, and discard expired readings.
  • Keep general quotas separate from model and code-review limits; fold duplicate verified account registrations in the display.

0.3.1

  • Expand every account underneath search, showing individual usage, identity, Active status, and direct Switch or Connect controls.
  • Keep search visible while long account lists scroll independently.
  • Reveal Accounts & Search when opening Threadline; add Show All Accounts and a named status-bar entry that preserves the current thread editor.

0.3.0

  • Keep live search, date sorting, account selectors, and usage visible across all views and long scrolling.
  • Show Created and Last used dates with four strict date sorts and an optional priority sort.
  • Refresh usage automatically on opening; preserve the last successful reading during loading or temporary failures.
  • Read owner-matched Claude quota cache and import existing Codex account manager profiles without copying credentials.
  • Switch the account used to reopen existing threads; support explicit Open with account.
  • Prefer the installed Claude extension CLI and wait for delayed native tabs before falling back to terminal onboarding.

0.2.0

  • Add isolated Codex and Claude account profiles, selected-account usage, and account switching for new threads.
  • Discover migrated Codex SQLite histories, preserve account ownership and native archive state, and explain shown/total counts.
  • Add manual tag/group creation, drag-and-drop organization, bulk actions, and persistent priorities.
  • Keep account-specific launches isolated, including restored terminals and shared DB-backed histories.

0.1.1

  • Use the supplied ANTRAZAL A for the extension, activity bar, editor tab, and dashboard icons.

0.1.0

  • Unified local Codex and Claude Code thread discovery.
  • Project tags, thread tags, custom groups, search, pinning, and archive.
  • Theme-aware dashboard and native folder tree with agent icons.
  • Native agent editor resume with editor-terminal fallback.
  • Parallel editor groups and conversation previews.

License

MIT License

Copyright (c) 2026 ANTRAZAL

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Third-party notices

Threadline is an independent ANTRAZAL utility. It is not affiliated with, endorsed by, or an official extension from OpenAI or Anthropic.

OpenAI, Codex, Claude, and Claude Code names and associated marks identify their respective providers. These marks remain the property of their owners. The MIT license for Threadline does not grant rights to third-party trademarks.

The provider glyphs in media/codex.svg, media/claude.svg, and media/provider-icons.ttf are used to identify thread and account providers. The font is generated from the shipped artwork by scripts/build-provider-icons.py.

The ANTRAZAL A artwork was supplied for Threadline's own branding. Development tools listed in package-lock.json retain their respective licenses; their packages are not bundled in the extension runtime.

Provider brand guidance: OpenAI and Anthropic. Attribution does not imply provider approval.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft