bitfolk 0.1.12 → 0.1.13

package/README.md

@@ -121,7 +121,7 @@ one prompt, and answers the tool's permission requests. `bitfolk tools` marks th
   `~/.bitfolk`). The tool gets no `BITFOLK_TOKEN` in its environment, only the file's path.
 - **The budget cap is approximate.** ACP has no spend limit, so the runner stops the turn once the cost the tool
   reports passes `--max-usd`. Cost arrives after it is spent, so one large call can go over; tools that report no
-  cost (or report it in credits) are limited only by `--timeout` and `--max-runs`.
+  cost (or report it in credits) are limited only by `--timeout` and `--max-runs`, when those are set.
 - The runner commits what an ACP tool leaves in its worktree. Each run is a new ACP session (no resume yet).
 - OpenCode and Hermes also speak ACP, but stay on their own adapters for now.
 
@@ -305,13 +305,18 @@ stops if the agent's worktree has uncommitted changes unless you add `--force`.
 
 ## Limits
 
+Sessions run with no spend cap, no hourly cap and no timeout unless you set one with `bitfolk set`. Pass `none` to
+turn a limit off again, for example `bitfolk set --max-usd none`.
+
 | Option | Default | |
 |---|---|---|
-| `--max-usd` | 1 | Hard spend cap per run (Claude Code's `--max-budget-usd`); approximate for ACP tools |
-| `--max-runs` | 6 | Most runs per rolling hour |
-| `--timeout` | 45 | Minutes before a run is stopped |
+| `--max-usd` | off | Hard spend cap per run (Claude Code's `--max-budget-usd`); approximate for ACP tools |
+| `--max-runs` | off | Most runs per rolling hour |
+| `--timeout` | off | Minutes before a run is stopped |
 | `--permission` | auto | `auto`: the runtime's auto mode. `safe`: edits in its worktree, `bitfolk-api`, read-mostly git, no curl. `bypass`: no prompts (only on a machine you'd hand over) |
 
+A session's sign-in to Bitfolk lasts 10 hours when no timeout is set.
+
 Bitfolk's own approval rules (`POST /v1/actions`) apply on top, wherever the agent runs.
 
 ## Report a bug