From e2597415bbf46f6a3bc27fffdd33d0f96090cfba Mon Sep 17 00:00:00 2001 From: saravmajestic Date: Wed, 15 Jul 2026 02:05:51 +0000 Subject: [PATCH 1/2] fix: [AI-7362] canonicalize legacy URLs (sh, my, dm, as hosts) - docs.altimate.sh/* -> https://help.altimate.ai/code/* - datamates-docs.myaltimate.com/* -> https://help.altimate.ai/datamates/* - www.altimate.sh/benchmarks -> https://altimate.ai/benchmarks/ Installer paths (altimate.sh/install, install.ps1) untouched. docs.altimate.ai refs deferred pending slug map from MAR-268 (1 ref in CHANGELOG.md). docs/docs/CNAME and docs/mkdocs.yml left unchanged (site self-config). script/upstream/ excluded (intentional branding/redirect map). --- CHANGELOG.md | 10 ++-- README.md | 4 +- docs/docs/configure/providers.md | 2 +- docs/docs/develop/ecosystem.md | 2 +- docs/docs/getting-started/index.md | 2 +- docs/docs/getting-started/quickstart-new.md | 2 +- docs/docs/llms.txt | 50 +++++++++---------- docs/docs/usage/ide.md | 4 +- packages/opencode/src/cli/cmd/providers.ts | 2 +- .../opencode/src/session/prompt/anthropic.txt | 2 +- packages/tui/src/app.tsx | 2 +- 11 files changed, 41 insertions(+), 41 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 3152f572bc..d52e10dc96 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -155,7 +155,7 @@ A plan-mode reliability patch for the hosted gateway and other non-Anthropic mod ### Fixed - **Plan mode no longer refuses benign requests on `altimate-default` and other non-Anthropic models.** The root cause was *how* altimate-code delivers its own plan instructions: a ``-wrapped block attached as user-role text. Claude is trained to read that tag as authoritative system guidance, but GPT-5.x, Gemini, and other non-Anthropic models pattern-matched the same block — carrying `STRICTLY FORBIDDEN` / `ZERO exceptions` / `MUST` language — as a **prompt-injection attempt** and declined, returning *"I'm sorry, but I cannot assist with that request."* for ordinary developer tasks. altimate-code now **hoists those self-injected reminders into proper `role:"system"` messages** for non-Anthropic models, so they arrive as instructions rather than suspect user input; Anthropic models are unchanged. The hoist is scoped by **provenance** to altimate-code's own reminder parts — user-supplied files, MCP-resource bodies, and `data:`-URL content can never gain system-role priority, even when they begin with ``. Gateway models are routed by `model.family` (via a shared `familyVendor` classifier) so a Claude- or Gemini-backed gateway model lands on the right base prompt instead of an Anthropic-style fallback. (#887, #888) -- **The "plan agent used no tools" warning is accurate — and no longer false-fires.** Previously the warning blamed the model's *tool-use capability* (misleading — these models are fully tool-capable) and could fire on the final text-only step of a **successful** multi-step plan session, making a working session look broken. The trip-wire now scans the conversation history for prior tool calls, so a session that already explored the codebase isn't flagged. When it does fire, the copy describes the observed symptom only ("stopped without calling any tools"), lists the likely causes, and offers concrete recoveries — ask it to investigate first, rephrase, or, if it keeps refusing, `/model` to a tier more eager to explore. The plan agent is also now instructed to **read or search the codebase before drafting** any plan, with an explicit escape hatch for trivial, fully-specified changes. See [Plan mode](https://docs.altimate.sh/data-engineering/agent-modes/#plan) and [Troubleshooting](https://docs.altimate.sh/reference/troubleshooting/). (#888) +- **The "plan agent used no tools" warning is accurate — and no longer false-fires.** Previously the warning blamed the model's *tool-use capability* (misleading — these models are fully tool-capable) and could fire on the final text-only step of a **successful** multi-step plan session, making a working session look broken. The trip-wire now scans the conversation history for prior tool calls, so a session that already explored the codebase isn't flagged. When it does fire, the copy describes the observed symptom only ("stopped without calling any tools"), lists the likely causes, and offers concrete recoveries — ask it to investigate first, rephrase, or, if it keeps refusing, `/model` to a tier more eager to explore. The plan agent is also now instructed to **read or search the codebase before drafting** any plan, with an explicit escape hatch for trivial, fully-specified changes. See [Plan mode](https://help.altimate.ai/code/data-engineering/agent-modes/#plan) and [Troubleshooting](https://help.altimate.ai/code/reference/troubleshooting/). (#888) ## [0.8.2] - 2026-06-03 @@ -163,7 +163,7 @@ A small correctness patch. The dbt PR reviewer's deterministic engine never requ ### Fixed -- **`dbt_pr_review` no longer implies it needs an altimate API key.** The native `altimate-core` engine behind the reviewer (column-lineage blast radius, query equivalence, PII classification, A–F grade) runs **fully offline** via the bundled napi binary — there is no `altimate_core.init` and no API-key gate in that path. Two tool descriptions (`altimate_core_column_lineage`, `altimate_core_track_lineage`) still carried a stale Python-bridge-era line claiming *"Requires `altimate_core.init()` with API key"*, so a stuck **lint-only** run was mis-diagnosed as missing auth. The descriptions now state the tools run offline with no key. **Lint-only actually means the dbt `manifest.json` didn't resolve** (wrong path, stale manifest, or wrong working directory) — the [dbt PR Review docs](https://docs.altimate.sh/usage/dbt-pr-review/) now spell out how to fix it. The only thing that ever needs a key is the optional advisory LLM lane, which can never block a verdict. (#882) +- **`dbt_pr_review` no longer implies it needs an altimate API key.** The native `altimate-core` engine behind the reviewer (column-lineage blast radius, query equivalence, PII classification, A–F grade) runs **fully offline** via the bundled napi binary — there is no `altimate_core.init` and no API-key gate in that path. Two tool descriptions (`altimate_core_column_lineage`, `altimate_core_track_lineage`) still carried a stale Python-bridge-era line claiming *"Requires `altimate_core.init()` with API key"*, so a stuck **lint-only** run was mis-diagnosed as missing auth. The descriptions now state the tools run offline with no key. **Lint-only actually means the dbt `manifest.json` didn't resolve** (wrong path, stale manifest, or wrong working directory) — the [dbt PR Review docs](https://help.altimate.ai/code/usage/dbt-pr-review/) now spell out how to fix it. The only thing that ever needs a key is the optional advisory LLM lane, which can never block a verdict. (#882) ## [0.8.1] - 2026-06-02 @@ -171,7 +171,7 @@ A reliability + correctness patch on top of 0.8.0. Highlights: **8 new Snowflake ### Added -- **Snowflake Cortex — 8 new selectable models.** Closes the drift between altimate-code's hardcoded Cortex model list and Snowflake's current regional-availability matrix: adds `claude-opus-4-7`, `openai-gpt-5.1`, `openai-gpt-5.2`, `llama4-scout`, `llama3.3-70b`, `snowflake-llama-3.1-405b`, `mixtral-8x7b`, and `gemini-3.1-pro` (Claude + OpenAI tool-capable; the rest chat-only, the conservative default until tool calling is verified on Cortex). When Cortex adds a model before the next release, you can now add it yourself under `provider["snowflake-cortex"].models` in `altimate-code.json` and it merges into the picker — no fork, no waiting. See [Snowflake Cortex provider docs](https://docs.altimate.sh/configure/providers/). (#866) +- **Snowflake Cortex — 8 new selectable models.** Closes the drift between altimate-code's hardcoded Cortex model list and Snowflake's current regional-availability matrix: adds `claude-opus-4-7`, `openai-gpt-5.1`, `openai-gpt-5.2`, `llama4-scout`, `llama3.3-70b`, `snowflake-llama-3.1-405b`, `mixtral-8x7b`, and `gemini-3.1-pro` (Claude + OpenAI tool-capable; the rest chat-only, the conservative default until tool calling is verified on Cortex). When Cortex adds a model before the next release, you can now add it yourself under `provider["snowflake-cortex"].models` in `altimate-code.json` and it merges into the picker — no fork, no waiting. See [Snowflake Cortex provider docs](https://help.altimate.ai/code/configure/providers/). (#866) ### Fixed @@ -182,7 +182,7 @@ Headlined by **dbt PR Review** — a Cloudflare-style, dbt/SQL-specialized code ### Added -- **dbt PR Review — signed, deterministic verdicts on dbt pull requests.** New `altimate review` CLI command and a composite GitHub Action (`github/review`). The deterministic engine (column-lineage / DAG blast radius, query equivalence on before/after model SQL, PII classification, A–F grade + anti-pattern lint) is the **only** layer that can block; an optional LLM reviewer is clamped to ≤ warning and excluded from the gate, so a `REQUEST_CHANGES` is always provable and replayable. Runs in CI with **zero warehouse access** (consumes `dbt compile` artifacts), and the verdict is HMAC-signable and tamper-evident. `comment` mode never blocks; `gate` mode fails the check on `REQUEST_CHANGES`. The advisory model/credentials are configured on the Action (hosted `altimate_api_key`, or bring-your-own `model` + `model_api_key`); omit them to run deterministic-only. See [dbt PR Review docs](https://docs.altimate.sh/usage/dbt-pr-review/) and the copy-paste workflow in `github/review/examples/`. Depends on `@altimateai/altimate-core` ≥ 0.4.0. (#856) +- **dbt PR Review — signed, deterministic verdicts on dbt pull requests.** New `altimate review` CLI command and a composite GitHub Action (`github/review`). The deterministic engine (column-lineage / DAG blast radius, query equivalence on before/after model SQL, PII classification, A–F grade + anti-pattern lint) is the **only** layer that can block; an optional LLM reviewer is clamped to ≤ warning and excluded from the gate, so a `REQUEST_CHANGES` is always provable and replayable. Runs in CI with **zero warehouse access** (consumes `dbt compile` artifacts), and the verdict is HMAC-signable and tamper-evident. `comment` mode never blocks; `gate` mode fails the check on `REQUEST_CHANGES`. The advisory model/credentials are configured on the Action (hosted `altimate_api_key`, or bring-your-own `model` + `model_api_key`); omit them to run deterministic-only. See [dbt PR Review docs](https://help.altimate.ai/code/usage/dbt-pr-review/) and the copy-paste workflow in `github/review/examples/`. Depends on `@altimateai/altimate-core` ≥ 0.4.0. (#856) - **Native Trino driver.** First-class Trino support over HTTP(S) with catalog/schema introspection and None / Basic / Bearer-token auth. **Migration note:** the dbt `trino` adapter previously mapped to the PostgreSQL driver; it now uses the native driver. Existing profiles are auto-aliased (`database` → `catalog`, `token` → `access_token`) and otherwise compatible. `trino-client` is an optional dependency — install it (`npm install trino-client`) to use Trino. (#795) - **Completion-gate validator framework.** A new opt-in harness-side check that runs after the LLM declares `finish === "stop"`. Two built-in @@ -196,7 +196,7 @@ Headlined by **dbt PR Review** — a Cloudflare-style, dbt/SQL-specialized code caught" rates without blocking). Default is **off** with zero overhead. Two new telemetry events (`validator_check`, `validator_retries_exhausted`). Configuration via `ALTIMATE_VALIDATORS_{MAX_RETRIES,TIMEOUT_MS,CONCURRENCY,DEBUG}`. - See [Validators docs](https://docs.altimate.sh/data-engineering/validators/) + See [Validators docs](https://help.altimate.ai/code/data-engineering/validators/) for the full reference, performance characteristics, and the phased rollout plan. (#849) diff --git a/README.md b/README.md index 4b51dcb128..7650ace3fd 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ into CI pipelines and orchestration DAGs. Precision data tooling for any LLM. [![npm](https://img.shields.io/npm/v/altimate-code)](https://www.npmjs.com/package/altimate-code) [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](./LICENSE) [![Slack](https://img.shields.io/badge/Slack-Join%20Community-4A154B?logo=slack)](https://altimate.studio/join-agentic-data-engineering-slack) -[![Docs](https://img.shields.io/badge/docs-docs.altimate.sh-blue)](https://docs.altimate.sh) +[![Docs](https://img.shields.io/badge/docs-help.altimate.ai%2Fcode-blue)](https://help.altimate.ai/code) [![Install GitHub App](https://img.shields.io/badge/GitHub-Install%20App-24292f?logo=github)](https://github.com/apps/altimate-code-agent/installations/new) [![Live dbt review](https://img.shields.io/badge/dbt-Live%20PR%20Demo-ff694b?logo=dbt)](https://github.com/AltimateAI/dbt-pr-review-demo/pulls) @@ -185,7 +185,7 @@ Each mode has scoped permissions, tool access, and SQL write-access control. | **Analyst** | Explore data, run SELECT queries, FinOps analysis, and generate insights | Read-only enforced (SELECT only, no file writes) | | **Plan** | Outline an approach before acting | Minimal (read files only, no SQL or bash) | -> **New to altimate?** Start with **Analyst mode** — it's read-only and safe to run against production connections. Need specialized workflows (validation, migration, research)? Create [custom agent modes](https://docs.altimate.sh). +> **New to altimate?** Start with **Analyst mode** — it's read-only and safe to run against production connections. Need specialized workflows (validation, migration, research)? Create [custom agent modes](https://help.altimate.ai/code). ## Supported Warehouses diff --git a/docs/docs/configure/providers.md b/docs/docs/configure/providers.md index be552e6de1..0689a6a0b1 100644 --- a/docs/docs/configure/providers.md +++ b/docs/docs/configure/providers.md @@ -36,7 +36,7 @@ Managed LLM access with dynamic routing across Sonnet 4.6, Opus 4.6, GPT-5.4, GP } ``` -For pricing, security, and data handling details, see the [Altimate LLM Gateway guide](https://datamates-docs.myaltimate.com/user-guide/components/llm-gateway/). +For pricing, security, and data handling details, see the [Altimate LLM Gateway guide](https://help.altimate.ai/datamates/user-guide/components/llm-gateway/). !!! tip "Automatic model selection" When Altimate credentials are configured and no model is explicitly chosen, the Altimate LLM Gateway is selected automatically. You can override this by setting `model` in your config or by restricting the `provider` section to specific providers only. diff --git a/docs/docs/develop/ecosystem.md b/docs/docs/develop/ecosystem.md index b3f67582ad..be68eee84a 100644 --- a/docs/docs/develop/ecosystem.md +++ b/docs/docs/develop/ecosystem.md @@ -15,7 +15,7 @@ altimate has a growing ecosystem of plugins, tools, and integrations. - **GitHub Actions**: Automated PR review and issue triage - **GitLab CI**: Merge request analysis - **VS Code / Cursor / Windsurf**: [IDE integration](../usage/ide.md) via the Datamates extension -- **[Datamates](https://datamates-docs.myaltimate.com/)**: AI teammates platform with MCP integrations, Knowledge Hub, Memory, and Guardrails +- **[Datamates](https://help.altimate.ai/datamates/)**: AI teammates platform with MCP integrations, Knowledge Hub, Memory, and Guardrails - **MCP**: Model Context Protocol servers - **ACP**: Agent Communication Protocol for editors diff --git a/docs/docs/getting-started/index.md b/docs/docs/getting-started/index.md index ec0bafd335..333f88e25c 100644 --- a/docs/docs/getting-started/index.md +++ b/docs/docs/getting-started/index.md @@ -171,7 +171,7 @@ Altimate Code goes the other direction. It connects to your **entire** stack and | **Column-Level Lineage** | 100% edge match across 500 queries with complex joins, CTEs, and subqueries. | | **Snowflake Query Optimization (TPC-H)** | 16.8% average execution speedup (3.6x vs baseline). | -

[:octicons-arrow-right-24: Full benchmark details](https://www.altimate.sh/benchmarks)

+

[:octicons-arrow-right-24: Full benchmark details](https://altimate.ai/benchmarks/)

--- diff --git a/docs/docs/getting-started/quickstart-new.md b/docs/docs/getting-started/quickstart-new.md index a2752b951b..055b8d835c 100644 --- a/docs/docs/getting-started/quickstart-new.md +++ b/docs/docs/getting-started/quickstart-new.md @@ -29,7 +29,7 @@ altimate ``` !!! tip "Don't want to manage API keys?" - The [Altimate LLM Gateway](https://datamates-docs.myaltimate.com/user-guide/components/llm-gateway/) gives you 10M tokens free — no API keys needed. It dynamically routes to the best model for each task across Sonnet 4.6, Opus 4.6, GPT-5.4, and more. + The [Altimate LLM Gateway](https://help.altimate.ai/datamates/user-guide/components/llm-gateway/) gives you 10M tokens free — no API keys needed. It dynamically routes to the best model for each task across Sonnet 4.6, Opus 4.6, GPT-5.4, and more. --- diff --git a/docs/docs/llms.txt b/docs/docs/llms.txt index f287812765..63f78b0d5b 100644 --- a/docs/docs/llms.txt +++ b/docs/docs/llms.txt @@ -1,42 +1,42 @@ # altimate-code llms.txt # AI-friendly documentation index for altimate-code # Generated: 2026-03-18 | Version: v0.5.0 -# Source: https://docs.altimate.sh +# Source: https://help.altimate.ai/code > altimate-code is an open-source data engineering harness with 100+ tools for building, validating, optimizing, and shipping data products. Use in your terminal, CI pipeline, orchestration DAGs, or as the tool layer for your data agents. Includes a deterministic SQL Intelligence Engine (100% F1 across 1,077 queries), column-level lineage, FinOps analysis, PII detection, and dbt integration. Works with any LLM provider. Local-first, MIT-licensed. ## Get Started -- [Quickstart (5 min)](https://docs.altimate.sh/quickstart/): Install altimate, configure your LLM provider, connect your warehouse, and run your first query in under 5 minutes. -- [Full Setup Guide](https://docs.altimate.sh/getting-started/): Complete installation, warehouse configuration for all 8 supported warehouses, LLM provider setup, and first-run walkthrough. -- [Network & Proxy](https://docs.altimate.sh/reference/network/): Proxy configuration, CA certificate setup, firewall requirements. +- [Quickstart (5 min)](https://help.altimate.ai/code/quickstart/): Install altimate, configure your LLM provider, connect your warehouse, and run your first query in under 5 minutes. +- [Full Setup Guide](https://help.altimate.ai/code/getting-started/): Complete installation, warehouse configuration for all 8 supported warehouses, LLM provider setup, and first-run walkthrough. +- [Network & Proxy](https://help.altimate.ai/code/reference/network/): Proxy configuration, CA certificate setup, firewall requirements. ## Data Engineering -- [Agent Modes](https://docs.altimate.sh/data-engineering/agent-modes/): 7 specialized agents (Builder, Analyst, Validator, Migrator, Researcher, Trainer, Executive), each with scoped permissions and purpose-built tool access. Builder has full read/write; Analyst has read-only enforced. -- [Training Overview](https://docs.altimate.sh/data-engineering/training/): How to teach altimate project-specific patterns, naming conventions, and corrections that persist across sessions and team members. -- [Team Deployment](https://docs.altimate.sh/data-engineering/training/team-deployment/): How to commit training to git so your entire team inherits SQL conventions automatically. -- [SQL Tools](https://docs.altimate.sh/data-engineering/tools/sql-tools/): 9 SQL analysis tools with 19 anti-pattern rules. 100% F1 accuracy on 1,077 benchmark queries. -- [Schema Tools](https://docs.altimate.sh/data-engineering/tools/schema-tools/): Warehouse schema introspection, metadata indexing, and column-level analysis tools. -- [FinOps Tools](https://docs.altimate.sh/data-engineering/tools/finops-tools/): Credit analysis, expensive query detection, warehouse right-sizing, unused resource cleanup, RBAC auditing. -- [Lineage Tools](https://docs.altimate.sh/data-engineering/tools/lineage-tools/): Column-level lineage extraction from SQL. 100% edge-match accuracy on 500 benchmark queries. -- [dbt Tools](https://docs.altimate.sh/data-engineering/tools/dbt-tools/): dbt manifest parsing, test generation, model scaffolding, incremental logic detection. -- [Warehouse Tools](https://docs.altimate.sh/data-engineering/tools/warehouse-tools/): Direct connectivity to Snowflake, BigQuery, Databricks, PostgreSQL, Redshift, DuckDB, MySQL, SQL Server. -- [Memory Tools](https://docs.altimate.sh/data-engineering/tools/memory-tools/): Session memory, persistent corrections, and team training storage. -- [Cost Optimization Guide](https://docs.altimate.sh/data-engineering/guides/cost-optimization/): Step-by-step warehouse cost reduction with before/after SQL examples and savings estimates. -- [Migration Guide](https://docs.altimate.sh/data-engineering/guides/migration/): Cross-warehouse SQL migration with side-by-side examples. -- [CI & Headless Mode](https://docs.altimate.sh/data-engineering/guides/ci-headless/): Non-interactive use in GitHub Actions, scheduled jobs, and pre-commit hooks. +- [Agent Modes](https://help.altimate.ai/code/data-engineering/agent-modes/): 7 specialized agents (Builder, Analyst, Validator, Migrator, Researcher, Trainer, Executive), each with scoped permissions and purpose-built tool access. Builder has full read/write; Analyst has read-only enforced. +- [Training Overview](https://help.altimate.ai/code/data-engineering/training/): How to teach altimate project-specific patterns, naming conventions, and corrections that persist across sessions and team members. +- [Team Deployment](https://help.altimate.ai/code/data-engineering/training/team-deployment/): How to commit training to git so your entire team inherits SQL conventions automatically. +- [SQL Tools](https://help.altimate.ai/code/data-engineering/tools/sql-tools/): 9 SQL analysis tools with 19 anti-pattern rules. 100% F1 accuracy on 1,077 benchmark queries. +- [Schema Tools](https://help.altimate.ai/code/data-engineering/tools/schema-tools/): Warehouse schema introspection, metadata indexing, and column-level analysis tools. +- [FinOps Tools](https://help.altimate.ai/code/data-engineering/tools/finops-tools/): Credit analysis, expensive query detection, warehouse right-sizing, unused resource cleanup, RBAC auditing. +- [Lineage Tools](https://help.altimate.ai/code/data-engineering/tools/lineage-tools/): Column-level lineage extraction from SQL. 100% edge-match accuracy on 500 benchmark queries. +- [dbt Tools](https://help.altimate.ai/code/data-engineering/tools/dbt-tools/): dbt manifest parsing, test generation, model scaffolding, incremental logic detection. +- [Warehouse Tools](https://help.altimate.ai/code/data-engineering/tools/warehouse-tools/): Direct connectivity to Snowflake, BigQuery, Databricks, PostgreSQL, Redshift, DuckDB, MySQL, SQL Server. +- [Memory Tools](https://help.altimate.ai/code/data-engineering/tools/memory-tools/): Session memory, persistent corrections, and team training storage. +- [Cost Optimization Guide](https://help.altimate.ai/code/data-engineering/guides/cost-optimization/): Step-by-step warehouse cost reduction with before/after SQL examples and savings estimates. +- [Migration Guide](https://help.altimate.ai/code/data-engineering/guides/migration/): Cross-warehouse SQL migration with side-by-side examples. +- [CI & Headless Mode](https://help.altimate.ai/code/data-engineering/guides/ci-headless/): Non-interactive use in GitHub Actions, scheduled jobs, and pre-commit hooks. ## Configure -- [Configuration Overview](https://docs.altimate.sh/configure/config/): Full altimate-code.json schema, value substitution, project structure, experimental flags. -- [Providers](https://docs.altimate.sh/configure/providers/): 17 LLM provider configurations with JSON examples: Anthropic, OpenAI, Google Gemini, Vertex AI, Amazon Bedrock, Azure OpenAI, Mistral, Groq, Ollama, and more. -- [Agent Skills](https://docs.altimate.sh/configure/skills/): How to configure, discover, and add custom skills. -- [Permissions](https://docs.altimate.sh/configure/permissions/): Permission levels, pattern matching, per-agent restrictions, deny rules for destructive SQL. -- [Tracing](https://docs.altimate.sh/configure/tracing/): Local-first observability covering trace schema, span types, live viewing, remote OTLP exporters, and crash recovery. -- [Telemetry](https://docs.altimate.sh/reference/telemetry/): 25 anonymized event types, privacy guarantees, opt-out instructions. +- [Configuration Overview](https://help.altimate.ai/code/configure/config/): Full altimate-code.json schema, value substitution, project structure, experimental flags. +- [Providers](https://help.altimate.ai/code/configure/providers/): 17 LLM provider configurations with JSON examples: Anthropic, OpenAI, Google Gemini, Vertex AI, Amazon Bedrock, Azure OpenAI, Mistral, Groq, Ollama, and more. +- [Agent Skills](https://help.altimate.ai/code/configure/skills/): How to configure, discover, and add custom skills. +- [Permissions](https://help.altimate.ai/code/configure/permissions/): Permission levels, pattern matching, per-agent restrictions, deny rules for destructive SQL. +- [Tracing](https://help.altimate.ai/code/configure/tracing/): Local-first observability covering trace schema, span types, live viewing, remote OTLP exporters, and crash recovery. +- [Telemetry](https://help.altimate.ai/code/reference/telemetry/): 25 anonymized event types, privacy guarantees, opt-out instructions. ## Reference -- [Security FAQ](https://docs.altimate.sh/reference/security-faq/): 12 Q&A pairs on data handling, credentials, permissions, network endpoints, and team hardening. -- [Troubleshooting](https://docs.altimate.sh/reference/troubleshooting/): 6 common issues with step-by-step fixes, including tool execution errors and warehouse connection setup. +- [Security FAQ](https://help.altimate.ai/code/reference/security-faq/): 12 Q&A pairs on data handling, credentials, permissions, network endpoints, and team hardening. +- [Troubleshooting](https://help.altimate.ai/code/reference/troubleshooting/): 6 common issues with step-by-step fixes, including tool execution errors and warehouse connection setup. diff --git a/docs/docs/usage/ide.md b/docs/docs/usage/ide.md index b41444f53c..d2fad74a01 100644 --- a/docs/docs/usage/ide.md +++ b/docs/docs/usage/ide.md @@ -50,8 +50,8 @@ The extension uses your existing `altimate-code.json` config. No additional IDE- You need an LLM to power the chat. Two options: - **BYOK (Bring Your Own Key)** — Free and unlimited. Configure any of the [35+ supported providers](../configure/providers.md) (Anthropic, OpenAI, AWS Bedrock, Azure OpenAI, etc.) -- **[Altimate LLM Gateway](https://datamates-docs.myaltimate.com/user-guide/components/llm-gateway/)** — Managed LLM access with dynamic model routing. 10M tokens free to get started — no API keys to manage +- **[Altimate LLM Gateway](https://help.altimate.ai/datamates/user-guide/components/llm-gateway/)** — Managed LLM access with dynamic model routing. 10M tokens free to get started — no API keys to manage ## Full Datamates Documentation -The Datamates extension offers additional capabilities beyond Altimate Code Chat, including MCP server integrations, Knowledge Hub, Memory Hub, and Guardrails. See the [Datamates documentation](https://datamates-docs.myaltimate.com/) for full setup guides, integration configuration, and feature details. +The Datamates extension offers additional capabilities beyond Altimate Code Chat, including MCP server integrations, Knowledge Hub, Memory Hub, and Guardrails. See the [Datamates documentation](https://help.altimate.ai/datamates/) for full setup guides, integration configuration, and feature details. diff --git a/packages/opencode/src/cli/cmd/providers.ts b/packages/opencode/src/cli/cmd/providers.ts index 0b02830043..8f8dfedb23 100644 --- a/packages/opencode/src/cli/cmd/providers.ts +++ b/packages/opencode/src/cli/cmd/providers.ts @@ -481,7 +481,7 @@ export const ProvidersLoginCommand = effectCmd({ if (["cloudflare", "cloudflare-ai-gateway"].includes(provider)) { yield* Prompt.log.info( // altimate_change start — altimate docs URL - "Cloudflare AI Gateway can be configured with CLOUDFLARE_GATEWAY_ID, CLOUDFLARE_ACCOUNT_ID, and CLOUDFLARE_API_TOKEN environment variables. Read more: https://docs.altimate.sh/configure/providers/", + "Cloudflare AI Gateway can be configured with CLOUDFLARE_GATEWAY_ID, CLOUDFLARE_ACCOUNT_ID, and CLOUDFLARE_API_TOKEN environment variables. Read more: https://help.altimate.ai/code/configure/providers/", // altimate_change end ) } diff --git a/packages/opencode/src/session/prompt/anthropic.txt b/packages/opencode/src/session/prompt/anthropic.txt index 238a012e00..25b1f711ee 100644 --- a/packages/opencode/src/session/prompt/anthropic.txt +++ b/packages/opencode/src/session/prompt/anthropic.txt @@ -10,7 +10,7 @@ If the user asks for help or wants to give feedback inform them of the following https://github.com/AltimateAI/altimate-code // altimate_change start — altimate docs URL -When the user directly asks about Altimate Code (eg. "can Altimate Code do...", "does Altimate Code have..."), or asks in second person (eg. "are you able...", "can you do..."), or asks how to use a specific Altimate Code feature (eg. implement a hook, write a slash command, or install an MCP server), use the WebFetch tool to gather information to answer the question from Altimate Code docs. The list of available docs is available at https://docs.altimate.sh +When the user directly asks about Altimate Code (eg. "can Altimate Code do...", "does Altimate Code have..."), or asks in second person (eg. "are you able...", "can you do..."), or asks how to use a specific Altimate Code feature (eg. implement a hook, write a slash command, or install an MCP server), use the WebFetch tool to gather information to answer the question from Altimate Code docs. The list of available docs is available at https://help.altimate.ai/code // altimate_change end # Tone and style diff --git a/packages/tui/src/app.tsx b/packages/tui/src/app.tsx index 11ee040f08..abb2a2d641 100644 --- a/packages/tui/src/app.tsx +++ b/packages/tui/src/app.tsx @@ -809,7 +809,7 @@ function App(props: { onSnapshot?: () => Promise; pluginHost: TuiPlugi title: "Open docs", run: () => { // altimate_change start — altimate docs URL - open("https://docs.altimate.sh").catch(() => {}) + open("https://help.altimate.ai/code").catch(() => {}) // altimate_change end dialog.clear() }, From 3ed3f47d58cfcbd44abf8f0924085d2558766249 Mon Sep 17 00:00:00 2001 From: saravmajestic Date: Thu, 16 Jul 2026 02:48:28 +0000 Subject: [PATCH 2/2] fix: [AI-7362] align default.txt and qwen.txt docs URL to help.altimate.ai/code --- packages/opencode/src/session/prompt/default.txt | 2 +- packages/opencode/src/session/prompt/qwen.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/opencode/src/session/prompt/default.txt b/packages/opencode/src/session/prompt/default.txt index 15d9533854..15c17f4d12 100644 --- a/packages/opencode/src/session/prompt/default.txt +++ b/packages/opencode/src/session/prompt/default.txt @@ -6,7 +6,7 @@ If the user asks for help or wants to give feedback inform them of the following - /help: Get help with using Altimate Code - To give feedback, users should report the issue at https://github.com/AltimateAI/altimate-code/issues -When the user directly asks about Altimate Code (eg 'can altimate do...', 'does altimate have...') or asks in second person (eg 'are you able...', 'can you do...'), first use the WebFetch tool to gather information to answer the question from Altimate docs at https://altimate.ai +When the user directly asks about Altimate Code (eg 'can altimate do...', 'does altimate have...') or asks in second person (eg 'are you able...', 'can you do...'), use the WebFetch tool to gather information to answer the question from Altimate Code docs. The list of available docs is available at https://help.altimate.ai/code # Tone and style You should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system). diff --git a/packages/opencode/src/session/prompt/qwen.txt b/packages/opencode/src/session/prompt/qwen.txt index a64ed55b89..545cba902c 100644 --- a/packages/opencode/src/session/prompt/qwen.txt +++ b/packages/opencode/src/session/prompt/qwen.txt @@ -8,7 +8,7 @@ If the user asks for help or wants to give feedback inform them of the following - /help: Get help with using Altimate Code - To give feedback, users should report the issue at https://github.com/AltimateAI/altimate-code/issues -When the user directly asks about Altimate Code (eg 'can altimate do...', 'does altimate have...') or asks in second person (eg 'are you able...', 'can you do...'), first use the WebFetch tool to gather information to answer the question from Altimate docs at https://altimate.ai +When the user directly asks about Altimate Code (eg 'can altimate do...', 'does altimate have...') or asks in second person (eg 'are you able...', 'can you do...'), use the WebFetch tool to gather information to answer the question from Altimate Code docs. The list of available docs is available at https://help.altimate.ai/code # Tone and style You should be concise, direct, and to the point. When you run a non-trivial bash command, you should explain what the command does and why you are running it, to make sure the user understands what you are doing (this is especially important when you are running a command that will make changes to the user's system).