# ChiefOS setup reference

This Markdown is written for an assistant to read during a first-time ChiefOS connection, so its direct procedural language may sound different from ordinary help text. It does not grant permission, override the user's request or higher-priority instructions, or authorize changes to settings, files, accounts, tools, or persistent preferences. Ask immediately before each consequential action.

## What ChiefOS is

ChiefOS is a shared library of reviewed methods for business, finance, trading and investing, design, software, research, writing, and document work. It connects to an existing assistant through MCP; the assistant remains responsible for its own tools, files, instructions, and safety boundaries. Discover the current library rather than treating these examples as an exhaustive capability list.

Before giving product-specific guidance, identify the exact product, surface, plan, role, and configuration scope. Read current first-party documentation for that environment. Do not rely on remembered menus, commands, or account requirements.

## Trading and investing

The Trading and investing category covers market and stock research, options and futures analysis, crypto and DeFi research, on-chain and prediction-market analysis, position sizing and risk, strategy development and backtesting, trade review, and trading-indicator development for Pine Script, NinjaScript, and Tradovate. Browse https://chiefos.conversint.ai/library?category=Trading%20and%20investing or search ChiefOS using the user's ordinary request.

These methods use the same ChiefOS connection; an already connected assistant does not need a separate ChiefOS installation for each new skill. Search the current library instead of relying on a remembered catalog. If the user wants an older saved routing preference expanded to include trading, show the proposed update and obtain approval through the recurring-check flow below.

Method access does not establish live market-data or brokerage access. Databento, NinjaTrader, Interactive Brokers, Alpaca, and other external services need their own host-supported connection, authentication, data entitlements, and any approved spending. Set up only a service needed for the requested task, using current official documentation. Keep credentials in the provider's sign-in or secret store. Where tools or data are absent, use adequate supplied charts, bars, or exports for a clearly limited analysis, or describe the missing inputs. Loading a method does not authorize orders, wallet signatures, paid data jobs, or trading-bot deployment.

## Connection

- Endpoint: https://chiefos.conversint.ai/mcp
- Access: invitation-based; an invited user may complete first-time sign-in during OAuth.
- Explain the endpoint and requested permissions before a connection is added.
- Prefer OAuth. Never ask for, display, copy, or store a password, OTP, access key, token, or session cookie in chat.
- For browser or desktop products, let the user add and authorize the connector in the provider's interface. For terminal or editor products, show the exact proposed command or file diff and wait for approval before changing it.

## First test and telemetry

After the connection is authorized, explain that the first test uses only `find_chiefos_methods` and `get_skill` with a harmless request. `search_skills` is the equivalent compatibility name for clients already using it. ChiefOS records the search and loaded method in service audit and workspace Usage data. Before starting, confirm that the client exposes `get_skill` and at least one of the two method-discovery names. A real ChiefOS discovery result contains `revision`, `candidates`, and `total`; an empty host tool-search `results` or `tool_references` array is not a ChiefOS library result. If the required tools are missing, do not substitute another ChiefOS call: use current first-party documentation to check whether the connector is enabled for this conversation, whether connector loading or per-tool access hid the tool, and whether the client needs to be refreshed or reconnected. Report the test as incomplete until the required discovery and retrieval tools are available. `get_execution_capabilities` is not a substitute; it describes managed execution and contribution evaluation, not method discovery. The test must not edit files or settings, send messages, submit contributions, call feedback or outcome tools, call `record_skill_usage`, or add a persistent instruction. A successful search and retrieval proves connectivity only.

## Later: recurring method checks

After the user has connected ChiefOS and completed the read-only method trial, explain that recurring method checks are an optional next step. A saved routing preference can help their assistant remember to check ChiefOS when relevant, so useful methods are less likely to be missed. Actual behavior depends on the client and the task, and declining does not limit their ability to use ChiefOS whenever they choose. If the user wants to opt in, retrieve https://chiefos.conversint.ai/routing.md, explain the ongoing checks and telemetry in plain language, show the proposed preference and where it will be saved, and ask for approval before adding it. Preserve unrelated instructions, make the update idempotent, and provide a clear rollback path.