Threadline — Codex & ClaudeKeep 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
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
For a downloaded preview package, run Extensions: Install from VSIX… and select the supplied 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 usageYour 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.
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 conversationsIn 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 settingsThreadline reads local Codex history from Modern Codex SQLite history requires built-in Node SQLite support or the system Search Threadline in VS Code Settings:
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 supportThreadline 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 noticeEffective 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 locallyThreadline 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 Data stored by ThreadlineVS 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 activityThreadline 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 removalStorage 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 supportThreadline'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, See Support for reporting guidance. Any data you choose to post in a public support channel is visible according to that channel's settings. SupportAfter 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
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
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 statusThe 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 notes0.3.8 — Preview
0.3.7
0.3.6
0.3.5
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.2.0
0.1.1
0.1.0
LicenseMIT 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 noticesThreadline 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 The ANTRAZAL A artwork was supplied for Threadline's own branding. Development tools listed in Provider brand guidance: OpenAI and Anthropic. Attribution does not imply provider approval. |