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 42f39d9
Browse filesBrowse the repository at this point in the historyBrowse files
Address PR review feedback and add personal access tokens page
- Drop the skill card file count (and its per-card detail fetch)
- Skip manage-only model provider queries for org members
- Keep the integration settings tab in the URL (?tab=)
- Restore the BYO "Connect machine" / "Share machines" header buttons
- Update model, skill, and machine docs for the new UI
- Split API tokens into org and personal access token pages
- Model combobox and credential secret field layout tweaks
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/api/authentication.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ A missing or invalid token returns `401` with code `unauthorized`. A valid token
40
40
41
41
Tokens are minted where a human can approve them — creating one is deliberately *not* possible with another API key:
42
42
43
-
-**Dashboard** — with **All projects** selected in the project switcher, open**API Tokens** and click **New token**. The full token is shown once.
43
+
-**Dashboard** — open your account menu at the bottom of the sidebar, choose**Personal access tokens**, and click **New token**. The full token is shown once.
44
44
-**Device login** — for CLIs and dev tools, below.
45
45
46
46
Only a hash is stored server-side, so save the token when it is shown.
@@ -49,7 +49,7 @@ Only a hash is stored server-side, so save the token when it is shown.
49
49
50
50
Services shouldn't run as a person — when that person leaves or their access changes, the integration breaks. An org API key is its own principal: it holds an org role (`admin` or `member`) and per-project roles, granted exactly like a member's.
51
51
52
-
Create one in the dashboard: with **All projects** selected in the project switcher, open **API Tokens**, switch to the **Organization**tab, and under **Organization API tokens** click **New token**. Pick a name and org role; the `omnara_org_v1_…` token is shown once. Then grant the key project roles from its detail panel — a member-role key sees nothing until you do, same as a human member.
52
+
Create one in the dashboard: with **All projects** selected in the project switcher, open **API Tokens** under **Access**(org admins only) and click **New token**. Pick a name and org role; the `omnara_org_v1_…` token is shown once. Then grant the key project roles from its detail panel — a member-role key sees nothing until you do, same as a human member.
53
53
54
54
Key management stays human-gated: creating, renaming, changing roles, and revoking all require a dashboard session, so one API key can never mint or escalate another. Listing and reading key metadata work with regular API auth ([List org API keys](/api-reference/endpoints/users-and-api-keys/list-org-api-keys)). Revocation is permanent and drops the key's org and project roles ([Revoke](/api-reference/endpoints/users-and-api-keys/revoke-an-org-api-key)).
55
55
@@ -148,4 +148,4 @@ Clients without OAuth support can pass a personal access token or org API key in
148
148
149
149
## Managing tokens
150
150
151
-
The **API Tokens** page — or [List personal access tokens](/api-reference/endpoints/users-and-api-keys/list-the-authenticated-users-personal-access-tokens) — shows your tokens with creation and last-used times, metadata only: the secret is never shown again. `last_used_at` tells you which tokens are actually alive; prune the rest, and [revoke](/api-reference/endpoints/users-and-api-keys/revoke-a-personal-access-token) immediately if a token leaks — revocation is permanent.
151
+
The **Personal access tokens** page in your account menu — or [List personal access tokens](/api-reference/endpoints/users-and-api-keys/list-the-authenticated-users-personal-access-tokens) — shows your tokens with creation and last-used times, metadata only: the secret is never shown again. `last_used_at` tells you which tokens are actually alive; prune the rest, and [revoke](/api-reference/endpoints/users-and-api-keys/revoke-a-personal-access-token) immediately if a token leaks — revocation is permanent.
Copy file name to clipboardExpand all lines: docs/machines/connect.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,9 +66,9 @@ Machines are org-level; a project's agents can only target machines granted to t
66
66
67
67
<Tabs>
68
68
<Tabtitle="Dashboard">
69
-
If you didn't share the machine while connecting it, select **All projects** in the project switcher, find its row under**Machines**, click **Share with project**, and select the project.
69
+
If you didn't share the machine while connecting it, select **All projects** in the project switcher, open **Machines**, and click**BYO Machines**. Open the machine's row actions, click **Share with project**, and select the project.
70
70
71
-
From a project, open its **Machines** page and click **Share machines**. The page's **Shared machines** table lists existing shares; click **Stop sharing** to revoke one.
71
+
From a project, open its **Machines** page and click **Share machines**. To see existing shares, click **BYO Machines**; open a row's actions and click **Stop sharing** to revoke one.
72
72
</Tab>
73
73
<Tabtitle="API">
74
74
If you didn't pass `project_ids` while connecting the machine, grant it afterwards:
Copy file name to clipboardExpand all lines: docs/organization/model-providers.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,11 +78,11 @@ A configured model (`mdl_…`) gives a provider model a name and runtime setting
78
78
<Tabtitle="Dashboard">
79
79
In **Add models**, select the detected models you want, or click **Skip for now**. The detected slug is used as the configured model name. Agent YAML must use the configured model name exactly.
80
80
81
-
To add models later, select **All projects** in the project switcher, open **Models**, and click **New model**. In **Add models**, choose the provider, then search the provider's models and check the ones you want, or type a slug that isn't listed and click its **Add … as a custom model** row. Click **Edit** on a selected row to set its **Name**, **Context**, and **Max output**; a row that still needs input shows **Needs details**. Optionally pick projects under **Share with**, then click the add button, which shows the count (for example, **Add 2 models**).
81
+
To add models later, select **All projects** in the project switcher, open **Models**, expand the provider's models, and click **Add model**; the provider's own page has the same button above its model list. In **Add models**, the provider is preselected; search the provider's models and check the ones you want, or type a slug that isn't listed and click its **Add … as a custom model** row. Click **Edit** on a selected row to set its **Name**, **Context**, and **Max output**; a row that still needs input shows **Needs details**. Optionally pick projects under **Share with**, then click the add button, which shows the count (for example, **Add 2 models**).
82
82
83
83
A provider can have several configured models for the same slug — for example, two names with different limits. Models the provider already has are marked **Added**; check one again to add another configuration under a different name.
84
84
85
-
To set the optional **Default output** allowance or change other settings later, open the model's row actions on the **Models** page and click **Edit**.
85
+
To set the optional **Default output** allowance or change other settings later, open the model's row actions under its provider on the **Models** page and click **Edit**.
Copy file name to clipboardExpand all lines: docs/quickstart.mdx
+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
@@ -35,7 +35,7 @@ Help me setup Omnara by fetching the Skill file here: https://github.com/omnara-
35
35
36
36
<Steps>
37
37
<Steptitle="Set up">
38
-
The CLI signs in through your browser; if you have not logged in yet, the first command that needs your account starts the login for you. The REST API and the SDK authenticate with an API token. In the web browser, select **All projects** in the project switcher, open**API Tokens**, click **New token**, and save the value.
38
+
The CLI signs in through your browser; if you have not logged in yet, the first command that needs your account starts the login for you. The REST API and the SDK authenticate with an API token. In the web browser, open your account menu at the bottom of the sidebar, choose**Personal access tokens**, click **New token**, and save the value.
Copy file name to clipboardExpand all lines: docs/tools/skills.mdx
+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
@@ -92,7 +92,7 @@ Each update creates the next revision; the skill's name cannot change.
92
92
The CLI has no update command. Running `omnara skills create` again with the same owner and skill name uploads the next revision.
93
93
</Tab>
94
94
<Tabtitle="Dashboard">
95
-
Open the skill's row menu and click **Edit**. The **SKILL.md** tab edits the instructions in place and keeps the other files; **Upload archive** replaces every file. Frontmatter errors are marked in the editor, and **Save** stays disabled until they are fixed.
95
+
Click the skill's name to open its page. Edit `SKILL.md`in place and click **Save**; the other files are kept. Frontmatter errors are marked in the editor, and **Save** stays disabled until they are fixed. To replace every file, click **Upload new version** and choose a new archive; the `SKILL.md` name must stay the same.
0 commit comments