Add Cortex Code quickstart; fix stale --task-name/--env examples - #8
Merged
sfc-gh-daxu merged 1 commit intoAug 28, 2026
Conversation
README's DuckDB examples still use --task-name and --env DB_TYPE=duckdb, which don't work on Harbor >= 0.21.0 (--task-name was renamed to -i/--include-task-name; --env only selects the environment type, not variables — use --config instead). Fixes both in the one-task and fast-30 examples. Adds docs/cortex-code.md covering what's specific to running the cortex-code agent: it needs its own Snowflake credentials for model access even on the hermetic DuckDB variant, disallowed_tools/cli_mode support landed after the latest Harbor release, and how to run a task without Harbor at all (by hand, or with Cortex Code driven directly inside the task container).
![snowflake-security-bot[bot]](https://avatars.githubusercontent.com/u/140554735?s=60&v=4){kind=small}
sfc-gh-daxu
approved these changes
Aug 28, 2026
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
2 participants
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
docs/cortex-code.md: setup notes specific to running thecortex-codeagent (it needs its own Snowflake credentials for modelaccess even on the hermetic DuckDB variant,
disallowed_tools/cli_modesupport for it only exists on Harbor main and not the latest release yet,
and how to run one task without Harbor at all — by hand, or with Cortex
Code driven directly inside a task container).
that don't work on current Harbor:
--task-nameno longer exists (renamedto
-i/--include-task-name), and--env DB_TYPE=duckdbdoesn't set anenvironment variable (
--env/-eselects the environment type — use theshipped
--config, which already setsenvironment.env). Also bumped the"tested with 0.20.x" note, since
--task-namedoesn't exist anywhere inthe current
harbor-framework/harborsource.codex/cortex-codeconfig mention).Why a separate doc instead of folding into the README
The README's existing Getting Started / DuckDB / Snowflake sections are
already agent-agnostic and cover common setup for all three bundled agents.
Cortex Code needed enough extra, agent-specific detail (its own credential
requirement, the current disallowed-tools/cli_mode gap, running it without
Harbor) that inlining all of it would have meant either duplicating the
common setup steps or bloating the README with content most non-Cortex-Code
users don't need. The new doc cross-links back to the relevant README
sections instead of repeating them.
Test plan
-i/--include-task-nameand--config(vs--task-name/--env DB_TYPE=...) against your own Harbor install, since I verifiedthis by reading harbor-framework/harbor's source/releases rather than
running the CLI myself.
docs/cortex-code.mdfor anything Cortex-Code-version-specificthat's since changed (
disallowed_tools/cli_modemerge status).