@quiel/cli 0.5.2 → 0.6.0

package/README.md

@@ -15,12 +15,16 @@ This package is the part that runs **on your machine**.
 - **Gives your agent the platform's tools over MCP** — take the next task, read project context and documents, read the files a human attached to the task, ask a human (and ask them to attach a file), request approval for a dangerous action, submit work.
 - **Installs hooks into your agent** so a shell command is checked against the project's trust profile *before* it runs. A command that matches a stop pattern is refused; a command that needs a human gets one.
 - **Keeps the connection and the task lease alive**, so the platform knows the task is being worked on and not abandoned.
+- **Lets the agent idle, and wakes it when work appears.** An empty queue is a normal state, not a failure: the agent stops its turn instead of asking for a task over and over. A background watcher notices when something is queued for it and wakes the session. Waiting costs a socket and a few bytes — not model turns, not context.
 - **Counts the tokens each task costs** and reports the totals, so a project can be looked at afterwards.
+- **Rescues unfinished work when your subscription limit runs out.** It commits what the agent managed and pushes it to the task's own branch, marked as interrupted, so the next person or agent continues from there instead of starting over. It never pushes to your main branch.
 
 It never sends the contents of your files anywhere — only file names, paths and commands. The token counters are numbers only: the client reads them from the agent's own transcript on your machine and sends the totals, never the conversation.
 
 Files go the other way only: a human attaches them in the browser, the agent downloads and reads them. The agent never uploads files of its own.
 
+**The client does commit and push, and only ever to the task's branch.** This happens in one case: your subscription limit runs out mid-task. Losing half a day's work is worse than an extra branch in the repository — but you should know it happens, and where.
+
 ## Requirements
 
 - Node.js 22 or newer
@@ -103,6 +107,8 @@ Everything goes into your project directory, so it is visible in `git status` an
 
 Plus one line in `.gitignore` for the directory the agent works in.
 
+For Claude Code, `Stop` gets **two** commands, and they are not duplicates: one decides whether the agent may stop, the other waits for work while it is stopped and wakes the session when something appears. The second is declared with `asyncRewake`, so it runs in the background and never blocks you.
+
 **Your token goes into none of them.** It is stored separately in `~/.quiel/credentials.json` with `0600` permissions, outside the repository. `.quiel.json` — the file that *is* committed — holds only the platform address, the project key, the agent id, its roles and which agent program you chose.
 
 Existing configuration is merged, not overwritten: other MCP servers, other hooks and your own comments survive. Running `init` again is the normal way to reconnect an agent, and it does not duplicate anything.
@@ -115,6 +121,7 @@ Existing configuration is merged, not overwritten: other MCP servers, other hook
 | `quiel connect` | Hold the connection to the platform |
 | `quiel status [--check]` | Show the project, the configured agent program, mode and current task |
 | `quiel mode auto\|manual` | Switch between autonomous and manual |
+| `quiel wait-for-task` | Wait for a task to appear and wake the sleeping session (started by a hook, not by you) |
 | `quiel mcp` | Run the MCP server over stdio (your agent starts this itself) |
 | `quiel hook <name> [--format …]` | Run a hook (your agent's configuration calls this) |