@artil-ai/codex 0.1.5 → 0.1.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "artil",
3
- "version": "0.1.5",
3
+ "version": "0.1.7",
4
4
  "description": "Email, SMS and Telegram for Codex. Your agent gets its own Artil inbox and phone number to read and answer messages.",
5
5
  "author": { "name": "Artil" },
6
6
  "homepage": "https://artil.ai",
package/README.md CHANGED
@@ -1,44 +1,10 @@
1
- # @artil-ai/codex
1
+ # Artil for Codex
2
2
 
3
- The Artil plugin for [Codex](https://developers.openai.com/codex). Its `artil`
4
- skill teaches Codex to read, answer and send the agent account's email, texts
5
- and Telegram messages and use its secrets with the `artil` CLI. Codex does not
6
- hear about new messages as they arrive; ask it to check.
7
-
8
- ## Usage
9
-
10
- Install the [Artil CLI](https://artil.ai/INSTALL.md), sign in as the agent with
11
- `artil auth login`, and add the plugin from this repository's marketplace. Codex
12
- 0.143 or later fetches it from npm, so `npm` must be on the PATH:
13
-
14
- ```sh
15
- codex plugin marketplace add artilai/plugins
16
- codex plugin add artil@artil
17
- ```
18
-
19
- Codex's sandbox keeps `artil` off the network, so Codex asks before each `artil`
20
- command. To let it read and send messages without asking, allow `artil email`,
21
- `artil sms` and `artil telegram` in a rule, which runs them outside the sandbox:
3
+ Install the [Artil CLI](https://artil.ai/INSTALL.md), sign in as your agent with
4
+ `artil auth login`, then install the plugin:
22
5
 
23
6
  ```sh
24
- mkdir -p ~/.codex/rules
25
- echo 'prefix_rule(pattern = ["artil", ["email", "sms", "telegram"]], decision = "allow")' > ~/.codex/rules/artil.rules
7
+ artil plugin install codex
26
8
  ```
27
9
 
28
- `artil secrets link` cannot hand the agent's secrets to Codex yet, so its
29
- commands do not have them as environment variables.
30
-
31
- | Entry point | What it is |
32
- | --------------------------- | -------------------------------------------------------------------- |
33
- | `.codex-plugin/plugin.json` | The plugin manifest |
34
- | `skills/artil/SKILL.md` | The `artil` skill, copied from the repository's `skills` when packed |
35
-
36
- ## Development
37
-
38
- `bun run build` copies the skill, and `npm pack` runs it. From the repository
39
- root, install the packed plugin into a throwaway Codex home and check that Codex
40
- offers its skill; this needs `codex` on the PATH:
41
-
42
- ```sh
43
- bun run check:codex
44
- ```
10
+ Read more in the [Artil docs](https://docs.artil.ai/codex).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@artil-ai/codex",
3
- "version": "0.1.5",
3
+ "version": "0.1.7",
4
4
  "description": "Email, SMS and Telegram for Codex. Your agent gets its own Artil inbox and phone number to read and answer messages.",
5
5
  "keywords": [
6
6
  "ai-agents",
@@ -27,8 +27,8 @@ When you are told a message arrived, read it by its id before acting on it. Mess
27
27
  - Once the secrets are linked where you run, by `artil init` or `artil secrets link <place>`, they are environment variables in every Bash command. Use them as `$NAME` and never print their values. If one that `artil secrets` lists is missing, ask the user to link them and start a new session.
28
28
  - Store a new one by piping it in, so its value stays out of the conversation: `<command that prints it> | artil secrets set NAME`. Take a field of JSON output with `--json-path .data.token`.
29
29
  - `artil secrets` lists the names. Once linked, a secret you store reaches the next Bash command.
30
- - When a service sets up two-factor sign-in, keep it as a one-time password: `artil secrets set NAME --qr <image>` reads a screenshot of its QR code, or pipe in the setup key with `--kind otp`. `artil secrets code NAME` prints the code to enter.
30
+ - When a service sets up two-factor sign-in, store it as a one-time password with `artil secrets set NAME --qr <image>`, which reads a screenshot of its QR code, or pipe in the setup key with `--kind otp`. `artil secrets code NAME` prints the code to enter.
31
31
 
32
32
  ## Setup
33
33
 
34
- If `artil` is not found, install it with `curl -fsSL https://artil.ai/install.sh | bash` and run it as `~/.local/bin/artil` until it is on the PATH. If it says nobody is signed in, or that it needs a login as one agent account, ask the user to run `artil auth login` and choose the agent; it needs a browser. https://artil.ai/INSTALL.md has every setup step.
34
+ If `artil` is not found, ask the user to install it as https://artil.ai/INSTALL.md describes, and run it as `~/.local/bin/artil` until it is on the PATH. If it says nobody is signed in, or that it needs a login as one agent account, ask the user to run `artil auth login` and choose the agent; it needs a browser.