You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1c54845
Browse filesBrowse the repository at this point in the historyBrowse files
- `hooks/altimate-code-workspace-rules.sh`: at session start, walk from
the host's directory up to
the repository root and match each folder as an exact JSON key of the
link cache (escaped, native form via `cygpath -w` on Windows), as the
CLI does. A link for a subfolder no longer starts the CLI from the
repository root, and `/x/app` no longer matches `/x/app-old`.
- Skip every event with `ALTIMATE_LEARN=0` (or `false`).
- Correct the comments on `$ROOT`, blocking and model calls per `Stop`.
- `tests/workspace-rules-hook.sh`: parse `hooks.json` and check each
event's argument and timeout; cover a start below a linked subfolder,
a root start with only a subfolder linked, a sibling-prefix link,
quote/backslash paths, Windows native keys and `ALTIMATE_LEARN`;
replace the fixed sleep with a sentinel; stop the slow stub on exit.
- `commands/rules.md`: show the edit here-doc flush left, branch on
`code` when `ok` is false and on `closed` when it is true, and never
repeat `--approve-anyway` without fresh confirmation.
- `PRIVACY.md`, `README.md`: approving the plugin means approving its
hooks (SessionStart, `UserPromptSubmit`, `Stop`); Codex may ask again
after upgrading from 1.1.0.
- `commands/rules.md`: a sandbox-queued answer is treated as answered
and never re-sent, including when a later `not_available` names it.
- `PRIVACY.md`: state what is gated by what, who can turn capture on,
the digest's contents and caps, that it goes to altimate-code's own
model rather than Codex's, and the rules telemetry the CLI sends; add a
revision date.
- `README.md`, `CHANGELOG.md`: `altimate learn …` throughout, bounded
session start, start in the linked folder, new clones and worktrees,
where proposals are answered, and the corrected gating.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: PRIVACY.md
+21-9Lines changed: 21 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
# Privacy Policy — Altimate Code plugin for Codex
2
2
3
3
**Effective date:** July 18, 2026
4
+
**Last revised:** November 4, 2026
4
5
**Applies to:** the `altimate-code` Codex plugin distributed from this repository, and the data flows it initiates through the [altimate-code](https://github.com/AltimateAI/altimate-code) CLI.
5
6
6
7
This policy supplements the Altimate AI [Privacy Policy](https://www.altimate.ai/privacy) and [Terms](https://www.altimate.ai/terms), which govern Altimate services generally. Where this document is silent, the master policy applies. Questions: **[email protected]**.
@@ -10,30 +11,39 @@ This policy supplements the Altimate AI [Privacy Policy](https://www.altimate.ai
10
11
## The short version
11
12
12
13
- The plugin itself collects **no data**. It is a routing layer (skills, slash commands, and session hooks) that tells Codex when to delegate a task to the altimate-code CLI installed on your machine.
13
-
- In a project linked to an Altimate workspace with learning on, its workspace-rules hooks hand your messages and the session transcript to the local altimate-code CLI, which keeps corrections on your machine and may send a digest to your LLM provider to word a proposed team rule. A proposal reaches your workspace only when you send or approve it. See [Workspace rules](#workspace-rules).
14
+
- In a project linked to an Altimate workspace, its workspace-rules hooks start the local altimate-code CLI, which pulls the workspace's approved team rules into the session. The hooks also hand your messages and the location of the session transcript to the CLI. With learning on, the CLI keeps corrections on your machine and may send a digest of the session, which can include file contents, command output and query results, to altimate-code's own model (not Codex's) to word a proposed team rule. A proposal reaches your workspace only when you send or approve it. The CLI also sends usage telemetry about team rules. See [Workspace rules](#workspace-rules).
14
15
- When a task **is** delegated, your task text is passed to the altimate-code CLI, which sends it to an LLM provider to plan and execute the work — the Altimate LLM Gateway by default, or a provider you configure (BYOK).
15
16
- Warehouse queries, dbt commands, and file edits run **locally on your machine, under your credentials**. Your warehouse credentials are never sent to Altimate.
16
-
- The plugin ships as opt-in. Adding the marketplace does not enable the plugin — you must explicitly install it from Codex's `/plugins` browser and approve its SessionStart hook before any delegation happens.
17
+
- The plugin ships as opt-in. Adding the marketplace does not enable the plugin — you must explicitly install it from Codex's `/plugins` browser and approve its hooks (SessionStart, UserPromptSubmit, Stop) before any delegation happens or any hook runs.
17
18
18
19
## What the plugin does and does not do
19
20
20
-
The plugin contains no executable service of its own. At session start, a hook prints a fixed, static text block describing the skill's capabilities. The workspace-rules hooks (see below) call the locally installed altimate-code CLI. The plugin does not phone home and does not collect analytics.
21
+
The plugin contains no executable service of its own. At session start, a hook prints a fixed, static text block describing the skill's capabilities. The workspace-rules hooks (see below) call the locally installed altimate-code CLI. The plugin itself does not phone home and does not collect analytics; the altimate-code CLI it starts sends usage telemetry (see [Usage telemetry](#usage-telemetry)).
21
22
22
23
Data leaves Codex's process only when the delegation skill, the `/altimate-code:altimate`, `/altimate-code:review` or `/altimate-code:rules` command, or a workspace-rules hook invokes the locally installed altimate-code CLI.
23
24
24
25
## Workspace rules
25
26
26
-
These hooks act only in a project linked to an Altimate workspace, with learning on, workspaces on and you signed in to Altimate. Otherwise the session-start hook reads only local altimate-code state and sends nothing, and the per-turn hooks do not run the CLI at all in a project without workspace rules state.
27
+
**When the hooks start the CLI.** At session start, the workspace-rules hook starts the local altimate-code CLI only in a repository that already has workspace rules state (`.altimate-code/learn/workspace-rules/rules.json` at the repository root), or when the folder the session starts in, or a folder above it in the repository, is named in altimate-code's local workspace link cache (`altimate-workspace-bindings.json`). Elsewhere it starts nothing. The hooks that run on each message and after each turn start the CLI only where workspace rules state exists. With `ALTIMATE_LEARN=0` (or `false`) no hook starts the CLI.
28
+
29
+
**What needs what.**
30
+
31
+
-*Team rules.* In a linked project, the CLI pulls the workspace's approved team rules at session start when workspaces are on (`ALTIMATE_DISABLE_WORKSPACE` is not set), you are signed in to Altimate and `ALTIMATE_LEARN` is not `0`. This does not depend on the learning setting.
32
+
-*Recording corrections and drafting proposed rules* also need learning on. Learning is on when you turned it on in the project (`altimate learn enable`) or, if you have made no choice of your own, when the workspace owner turned on the workspace's "Learn from sessions" setting. Your own choice (`altimate learn enable` or `altimate learn disable`) overrides the workspace setting, unless your organization enforces a policy.
33
+
- Where workspace rules state exists, the per-turn hooks hand each message you send and the location of the session transcript to the local CLI whether or not learning is on. When learning is off, you are signed out or the project is not linked, the CLI discards them and nothing leaves your machine.
34
+
35
+
**The digest used to word a proposed rule.** After a turn with new corrections, the CLI reads the Codex session transcript (its last 8 MB) and builds a digest of the session: your prompts, the input and output of each tool call (up to 300 and 400 characters per call, so file contents, command output and warehouse query results can appear), and the final reply, at most 24,000 characters in total. Secrets in the digest are masked; no other data is removed. The digest is sent to altimate-code's own model: the model set as `learn.model` in altimate-code's configuration, otherwise altimate-code's default model, which is the Altimate LLM Gateway or another provider configured for altimate-code. This is not the model Codex uses; it is a party that does not otherwise see your Codex session. If altimate-code has no model it can use, nothing is sent, and the next session start reports that the check failed. The CLI makes at most one such model call per check round, and a few per turn at most.
27
36
28
37
| Data | Where it goes | Retention |
29
38
|---|---|---|
30
39
| Your workspace's approved team rules | Pulled by the local CLI from your Altimate workspace, given to Codex as session context | Mirrored locally in the project's git-ignored `.altimate-code/` directory |
31
-
| Each message you send |The local CLIchecks it, with no model call; a message that reads as a correction is kept (secrets redacted) | Local only, in the project's git-ignored `.altimate-code/` directory |
32
-
| The session transcript, after a turn with new corrections | Read locally by the CLI; a bounded, redacted digest goes to your configured LLM provider to word one proposed rule |Local only; the provider's handling is as for delegated tasks above|
33
-
| A proposed rule, with an excerpt of your correction if your workspace allows quotes | Your Altimate workspace's review queue, only when you send or approve it in `/altimate-code:rules`| Per the Altimate Privacy Policy |
40
+
| Each message you send |Handed to the local CLI, which checks it with no model call; with learning on, a message that reads as a correction is kept (secrets redacted) | Local only, in the project's git-ignored `.altimate-code/` directory |
41
+
| The session transcript, after a turn with new corrections (learning on) | Read locally by the CLI; the digest described above goes to altimate-code's own model to word one proposed rule |The transcript stays local; the model provider's handling is as for delegated tasks below|
42
+
| A proposed rule, with an excerpt of your correction if your workspace allows quotes | Your Altimate workspace's review queue, only when you send or approve it in `/altimate-code:rules`or `altimate learn proposals`| Per the Altimate Privacy Policy |
34
43
| Rule usage counts (sessions a rule was shown in, corrections after it) | Your Altimate workspace | Per the Altimate Privacy Policy |
44
+
| Rules telemetry events: `rules_sync`, `rules_delivered`, `rule_drafted`, `rule_proposal_shown` (with the Codex session id, as `codex:<id>`), `rule_proposal_answered`, `rule_proposal_skipped`, `rule_remember_routed`. No rule text, prompts or file paths | Altimate's usage telemetry, as described in [Usage telemetry](#usage-telemetry)| As for usage telemetry; turned off with the telemetry opt-out there |
35
45
36
-
Turn this off with `altimate-code learn disable` in the project, `ALTIMATE_LEARN=0`, or the workspace's "Learn from sessions" setting.
46
+
Turn off recording and drafting with `altimate learn disable` in the project, or, for members who have made no choice of their own, with the workspace's "Learn from sessions" setting. `ALTIMATE_LEARN=0` turns off all of it, including the team rules pull, and the hooks then start nothing.
37
47
38
48
## Data flows when a task is delegated
39
49
@@ -72,7 +82,7 @@ All data transmitted to Altimate services is encrypted in transit using TLS. Alt
72
82
73
83
## Your choices
74
84
75
-
-**Don't install the plugin** — adding the marketplace makes it discoverable but does not install it; delegation happensonly after you install from Codex's `/plugins` browser and approve its SessionStart hook.
85
+
-**Don't install the plugin** — adding the marketplace makes it discoverable but does not install it; delegation happens, and its hooks run, only after you install from Codex's `/plugins` browser and approve its hooks (SessionStart, UserPromptSubmit, Stop).
76
86
-**Use BYOK** — route prompts directly to your own provider so Altimate never sees them.
77
87
-**Disable telemetry** — see above.
78
88
-**Contact us** — for access, correction, or deletion requests, email **[email protected]**.
@@ -85,6 +95,8 @@ The plugin and the altimate-code CLI are professional developer tools, not direc
85
95
86
96
We will update this document in this repository and revise the effective date when our practices change. Material changes to Altimate-wide practices are governed by the master [Privacy Policy](https://www.altimate.ai/privacy).
87
97
98
+
**November 4, 2026:** added [Workspace rules](#workspace-rules) (the workspace-rules hooks and `/altimate-code:rules` in plugin 1.2.0), and the rules telemetry the altimate-code CLI sends.
99
+
88
100
## Contact
89
101
90
102
Altimate Inc. · 440 North Wolfe Road #150, Sunnyvale, CA 94085, USA · +1 (650) 254-6266
The plugin ships a `SessionStart` hook that injects a short routing hint into the model's context so it prefers the `altimate-code` skill for warehouse-touching work. Codex does not run plugin-bundled hooks automatically — the first time you start a session with the plugin installed, Codex will prompt you to review and trust the hook definition. Approve it once and the hook fires in every subsequent session; skip it and the plugin still installs but the routing hint won't be delivered.
50
+
The plugin ships a `SessionStart` hook that injects a short routing hint into the model's context so it prefers the `altimate-code` skill for warehouse-touching work. Codex does not run plugin-bundled hooks automatically — the first time you start a session with the plugin installed, Codex will prompt you to review and trust the hook definition. Approve it once and the hook fires in every subsequent session; skip it and the plugin still installs but the routing hint won't be delivered. The same applies to the workspace-rules hooks (SessionStart, UserPromptSubmit, Stop; see Team rules): without them, no team rules are given and no corrections are proposed.
51
51
52
52
## Layout
53
53
@@ -59,7 +59,7 @@ altimate-codex-plugin/
59
59
├── .codex-plugin/
60
60
│ └── plugin.json # plugin manifest
61
61
├── hooks/
62
-
│ ├── hooks.json # SessionStarthook definition
62
+
│ ├── hooks.json # SessionStart, UserPromptSubmit and Stop hook definitions
Copy file name to clipboardExpand all lines: SECURITY.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ This plugin's skill forwards the user's task text to the [altimate-code](https:/
19
19
-**Warehouse queries and dbt commands** → executed locally under your credentials by the CLI; not forwarded.
20
20
-**Query results and file edits** → produced locally; the CLI writes an output file which the plugin surfaces back to Codex.
21
21
22
-
If you do not want prompts to leave Codex's process, do not install this plugin. Adding the marketplace only makes it discoverable in Codex's `/plugins` browser — no delegation happens until you explicitly install it and approve the SessionStart hook.
22
+
If you do not want prompts to leave Codex's process, do not install this plugin. Adding the marketplace only makes it discoverable in Codex's `/plugins` browser — no delegation happens until you explicitly install it and approve its hooks (SessionStart, UserPromptSubmit, Stop).
23
23
24
24
For the complete privacy policy covering the plugin and the altimate-code CLI, see [PRIVACY.md](./PRIVACY.md).
Copy file name to clipboardExpand all lines: plugins/altimate-code/CHANGELOG.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,10 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
11
11
- Corrections you make to Codex are recorded locally (UserPromptSubmit, no model call). After a turn, altimate-code checks them in the background (Stop) and keeps a proposed rule when you corrected the same topic in two sessions or corrected a team rule Codex was given.
12
12
- "Remember this as a team rule: …" said to Codex waits as a proposal (no model call).
13
13
-`/altimate-code:rules`: answer proposed rules (send for review, approve as owner, edit, save as memory, or "Not a rule"), and see the team rules and the review status of your proposals.
14
-
- The hooks run only in a linked project with learning on. They need an altimate-code release with `learn hook`; with an older one they do nothing.
14
+
- Session start runs altimate-code only in a repository with workspace rules state, or where the session's folder (or a folder above it in the repository) is in altimate-code's workspace link cache; the per-turn hooks run it only where workspace rules state exists. Team rules arrive in a linked project when you are signed in; recording corrections and drafting proposals also need learning on. `ALTIMATE_LEARN=0` turns all of it off and the hooks start nothing.
15
+
- Start the session in the linked folder or below it: with only a subfolder linked (a dbt project), a session started at the repository root gets no team rules.
16
+
- Codex may ask you to approve the plugin's hooks again after upgrading from 1.1.0.
17
+
- The hooks need an altimate-code release with `learn hook`; with an older one they do nothing.
0 commit comments