Open
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Restore .trim() on models API JSON to prevent syntax error in generated models-snapshot.ts - Fix archive path for scoped package names (@altimate/cli-*) in release tarball/zip creation - Remove gh release upload from build.ts (handled by github-release job) - Add CHANGELOG.md entry for v0.1.5 Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
- Redesign M as 5-wide with visible V-valley to distinguish from A - Change E top from full bar to open-right, distinguishing from T - Fix T with full-width crossbar and I as narrow column - Fix D shape in CODE - Render CODE in theme.accent (purple) instead of theme.primary (peach) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- publish.ts: change glob from `*/package.json` to `**/package.json` to find scoped package directories (@altimate/cli-*) which are 2 levels deep - release.yml: add skip-existing to PyPI publish so it doesn't fail when the engine version hasn't changed between releases Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The npm org is @AltimateAI, not @Altimate. Update all package names, workspace dependencies, imports, and documentation to use the correct scope so npm publish succeeds. Name mapping: - @altimate/cli → @altimateai/altimate-code - @altimate/cli-sdk → @altimateai/altimate-code-sdk - @altimate/cli-plugin → @altimateai/altimate-code-plugin - @altimate/cli-util → @altimateai/altimate-code-util - @altimate/cli-script → @altimateai/altimate-code-script Also updates publish.ts to emit the wrapper package as @altimateai/altimate-code (no -ai suffix) and hardcodes the bin entry to altimate-code. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Two issues: 1. TypeScript permission-task tests: test fixture wrote config to `opencode.json` but the config loader only looks for `altimate-code.json`. Updated fixture to use correct filename. 2. Python tests: `pytest: command not found` because pyproject.toml had no `dev` optional dependency group. Added `dev` extras with pytest and ruff. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* fix: rename opencode references to altimate-code in all test files Update test files to use the correct names after the config loader was renamed from opencode to altimate-code: - `opencode.json` → `altimate-code.json` - `.opencode/` → `.altimate-code/` - `.git/opencode` → `.git/altimate-code` - `OPENCODE_*` env vars → `ALTIMATE_CLI_*` - Cache dir `opencode` → `altimate-code` - Schema URL `opencode.ai` → `altimate-code.dev` Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: resolve remaining test failures and build import issue - Fix build.ts solid-plugin import to use bare specifier for monorepo hoisting - Update agent tests: "build" → "builder", "plan" → "analyst" for disabled fallback - Fix well-known config mock URL in config.test.ts - Fix message-v2 test: "OpenCode" → "Altimate CLI" - Fix retry.test.ts: replace unsupported test.concurrent with test - Fix read.test.ts: update agent name to "builder" - Fix agent-color.test.ts: update config keys to "builder" - Fix registry.test.ts: remove unpublished plugin dep from test fixture - Skip adding plugin dependency in local dev mode (installDependencies) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: address Sentry review comments and Python CI deps - Update theme schema URL from opencode.ai to altimate-code.dev (33 files) - Rename opencode references in ACP README.md and AGENTS.md docs - Update test fixture tmp dir prefix to altimate-code-test- - Install warehouse extras in Python CI for duckdb/boto3 test deps Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: Python CI — SqlGuardResult allows None data, restrict pytest to tests/ - Allow SqlGuardResult.data to be None (fixes lineage.check Pydantic error) - Set testpaths = ["tests"] in pyproject.toml to exclude src/test_local.py from pytest collection (it's a source module, not a test) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: resolve ruff lint errors in Python engine - Remove unused imports in server.py (duplicate imports, unused models) - Remove unused `json` import in schema/cache.py - Remove unused `os` import in sql/feedback_store.py - Add noqa for keyring availability check import Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use import.meta.resolve to find the @opentui/core package directory instead of hardcoding node_modules path, which fails with monorepo hoisting. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…aming - Build: output binary as altimate-code instead of opencode - Bin wrapper: look for @altimateai/altimate-code-* scoped packages - Postinstall: resolve @AltimateAI scoped platform packages - Publish: update Docker/AUR/Homebrew refs to AltimateAI/altimate-code - Publish: make Docker/AUR/Homebrew non-fatal (infra not set up yet) - Dockerfile: update binary paths and names Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Jérôme Benoit <jerome.benoit@piment-noir.org>
…sion (#15762) Co-authored-by: Test User <test@test.com> Co-authored-by: Shoubhit Dash <shoubhit2005@gmail.com>
Post-merge now runs build, test, and typecheck before declaring success. Stops on build failure; warns on test/typecheck failures (since some may be pre-existing). Co-Authored-By: Kai (Claude Opus 4.6) <noreply@anthropic.com>
chore: merge upstream opencode v1.2.20
- Add null guard to `NamedError.isInstance()` preventing `TypeError` on null input - Add Azure OpenAI overflow detection patterns (`the request was too long`, `maximum tokens for requested operation`) - Fix token estimation tests to use new content-aware ratio (3.7) - Fix compaction/prune config tests: `altimate-code.json` → `opencode.json` - Fix install test fixtures: `@opencode-ai/opencode` → `@altimateai/altimate-code` - Fix `bin/altimate-code` entry in `package.json` to point to dedicated wrapper - Fix test import paths for relocated modules (`bridge/client`, `bridge/engine`, `tool/project-scan`) - Add synthetic pending emission + bash output streaming to ACP agent event handler - Add `pendingEmitted` tracking set and clear bash snapshots on pending state Co-Authored-By: Kai (Claude Opus 4.6) <noreply@anthropic.com>
fix: resolve all test failures from fork restructure
`@gitlab/opencode-gitlab-auth` depends on `@opencode-ai/plugin@1.2.10` (npm) while the workspace has `@opencode-ai/plugin@1.2.20`. The `_HeyApiClient` protected property differs between versions, causing a TS2322 error. Cast to `PluginInstance` since the types are structurally compatible at runtime. Co-Authored-By: Kai (Claude Opus 4.6) <noreply@anthropic.com>
fix: resolve GitlabAuthPlugin type incompatibility
* chore: use ARC self-hosted runner for CI * chore: use ARC self-hosted runner for release workflow * fix: harden ARC runner migration with security and reliability safeguards - Fall back to `ubuntu-latest` for fork PRs to prevent untrusted code execution on self-hosted ARC runners - Add `timeout-minutes: 60` to all CI and release jobs (self-hosted runners have no default timeout unlike GitHub-hosted 6h limit) - Write `NPM_TOKEN` to `$RUNNER_TEMP/.npmrc` instead of `~/.npmrc` to prevent secret persistence on self-hosted runners - Set `NPM_CONFIG_USERCONFIG` to point publish step to temp `.npmrc` - Add `concurrency` group to CI workflow to cancel superseded runs --------- Co-authored-by: anandgupta42 <anand@altimate.ai>
ci: switch Windows tests to ARC self-hosted runner
…ck required tools)
Co-Authored-By: Kai (Claude Opus 4.6) <noreply@anthropic.com>
…onfig fix: restore TUI crash after upstream merge
fix: correct TEAM_MEMBERS ref from 'dev' to 'main' in pr-standards workflow
- Add `AltimateApi` client for datamate CRUD and integration resolution - Add `datamate` tool with 9 operations: list, show, create, update, delete, add (MCP connect), remove (MCP disconnect), list-integrations, status - Extract shared MCP config utilities (`resolveConfigPath`, `addMcpToConfig`, `removeMcpFromConfig`, `listMcpInConfig`) to `mcp/config.ts` - Add `/datamate-setup` skill for guided datamate onboarding - Register datamate tool in tool registry and TUI sync context - Add test suite for `AltimateApi` credential loading and API methods
feat: datamate manager — dynamic MCP server management
…tion - Add `skill-selector.ts` with `selectSkillsWithLLM()` — uses small model (Haiku 4.5 via `Provider.getSmallModel`) + `generateObject` to semantically select relevant skills based on user message and project fingerprint - Remove `partitionByFingerprint()` and `rescueByMessage()` from `tool/skill.ts` - Remove `tags` field from `Skill.Info` schema and all 51 SKILL.md files - Add 2 new dbt-labs skills: `migrating-dbt-core-to-fusion`, `migrating-dbt-project-across-platforms` - Rewrite tests with `SkillSelectorDeps` DI interface for model + generate mocking - Graceful fallback: returns all skills on timeout (3s), error, no model, or zero selection
Full benchmark infrastructure for evaluating altimate-code against the Spider 2.0-DBT leaderboard (68 dbt+DuckDB tasks). Includes setup, runner, evaluator, and reporting.
- Fix `sql_validate` → `altimate_core_validate` across all agent prompts - Improve analyst schema discovery and builder output discipline - Comment out non-builder agents for benchmark focus - Add retry limits to prevent infinite retry loops in session processor - Remove stale IMPLEMENTATION_PLAN.md
- Delete `altimate-setup` skill definition - Remove "Available Skills" section from `builder.txt` prompt - Skills were not improving benchmark performance (26.47% vs 32.35% baseline)
Instrument `altimate run` with Langfuse observability (activated via LANGFUSE_* env vars) so benchmark runs capture tool calls, tokens, cost, and timing as traces. After evaluation, traces are updated with benchmark_pass scores for end-to-end visibility in the Langfuse dashboard. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Generations previously had empty input (no context) and empty output when the model only produced tool calls. Now: - Input shows tool results from the preceding step - Output falls back to "[tool calls: read, write, ...]" when no text Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Rewrite builder prompt to reflect data engineer workflow (understand data → write → build → verify) instead of QA checklists - Remove cosmetic tools (format, grade, generate-tests, FinOps) that don't affect correctness - Deduplicate tool mentions (each tool listed once) - Patch deprecated dbt config keys (source-paths → model-paths, data-paths → seed-paths) in prepare_workspace to suppress warnings Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The v4 SDK renamed `score()` to `create_score()`. Use `create_score` with fallback to `score` for backwards compatibility. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
When the builder agent declares it's done, automatically inject a verification prompt into the same conversation. The verification step checks dbt build status, column order against YAML specs, and row counts against source data — fixing issues before the session ends. Also adds benchmark prompt improvements: column ordering guidance, date range bounds, row count verification, staging model preference, final build enforcement, and mandatory data inspection. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This reverts commit bd6eeeb.
✅ Tests — All PassedTypeScript — passedPython — passedTested at |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
What changed and why?
Test Plan
How was this tested?
Checklist