picocode 0.9.45 → 0.9.46

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.
Files changed (3) hide show
  1. package/README.md +25 -0
  2. package/dist/pico.js +19 -4
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -22,3 +22,28 @@ Requires node 24 or newer and ripgrep. Set at least one provider key in your env
22
22
  Run `pico` in a project directory. Type `/` to browse commands, or run `/help` for the full reference.
23
23
 
24
24
  Sessions are stored under `~/.pico` as jsonl event logs. AGENTS.md files are read automatically from the working directory up to the git root, and lazily from subdirectories as the agent touches them. User-defined prompt templates live in `~/.pico/commands` and `.pico/commands`, skills in `~/.pico/skills` and `.pico/skills`.
25
+
26
+ ## Obligatory feature list
27
+
28
+ - Multi-provider support
29
+ - ChatGPT/Codex subscription support through Codex OAuth
30
+ - Headless mode with text, JSON, and JSONL output
31
+ - Background shells, with a management UI
32
+ - Parallel background agents, with a management UI
33
+ - Full MCP support
34
+ - Project and global memories with on-demand recall and management
35
+ - Fast session, project, model, prompt, and file pickers
36
+ - Scheduled wake-ups and recurring agent tasks
37
+ - Skills and commands
38
+ - Image attachments (drag and drop or via file picker)
39
+ - Per-project config for memories, commands, skills, tools, and MCP servers
40
+
41
+ And quite a bit more, actually.
42
+
43
+ ## Tips
44
+
45
+ Pico can extend itself. Describe what you want and whether it should be available globally or only in the current project.
46
+
47
+ - Ask Pico to create a skill for you
48
+ - Ask Pico to create a command for you
49
+ - Ask Pico to create a tool for itself