one-code-extension 0.3.0 → 0.3.1

package/docs/guide/permissions-modes-and-auto-mode.md

@@ -1,5 +1,7 @@
 # Permissions, modes, and auto mode
 
+[← One Code user guide](README.md)
+
 Every tool call the model makes passes through One Code's permission gate
 before it runs. This page explains the permission modes, how to switch
 between them, how to write rules, what the approval prompt offers, and how
@@ -16,7 +18,7 @@ For each tool call, the gate checks the following in order:
 1. **Protected paths.** A write to a protected file or directory (see
    [Protected paths](#protected-paths)) is never approved automatically. In
    auto mode it goes to the classifier; in other modes it prompts you.
-   Allow rules do not cover protected paths.
+   Allow rules don't cover protected paths.
 2. **`deny` rules.** A matching `deny` rule blocks the call. `deny` always
    wins.
 3. **`ask` rules.** A matching `ask` rule prompts you, even in a mode that
@@ -96,7 +98,7 @@ Add `global` at the end to save it for every repository instead:
 ```
 
 To review the current mode and every loaded rule, including which project
-rules are trusted and which rules could not be parsed, run `/permissions`.
+rules are trusted and which rules couldn't be parsed, run `/permissions`.
 
 Rules One Code adds are saved under `~/.onecode`, never under `~/.claude`.
 
@@ -104,7 +106,7 @@ Rules One Code adds are saved under `~/.onecode`, never under `~/.claude`.
 
 A mode sets the default answer for actions no rule covers. **Auto is the
 default**, matching Claude Code: a classifier approves routine actions and
-stops risky ones, so you are not prompted for every step.
+stops risky ones, so you're not prompted for every step.
 
 | Mode | Badge | What it does |
 |---|---|---|
@@ -121,7 +123,7 @@ changes.
 ### Cycle modes with ctrl+q
 
 Press **ctrl+q** to cycle through manual, accept edits, plan, and auto.
-Two modes join the cycle only under conditions:
+Two modes join the cycle only under certain conditions:
 
 - **Auto** appears only when a model that can run the classifier is
   available. With no provider connected, the cycle skips it.
@@ -130,7 +132,7 @@ Two modes join the cycle only under conditions:
 **Don't ask** is never in the cycle; reach it with the `--permission-mode`
 flag or a settings file.
 
-Claude Code cycles modes with shift+tab. One Code cannot use that key
+Claude Code cycles modes with shift+tab. One Code can't use that key
 because pi reserves it for the reasoning-effort dial. On Windows and WSL,
 pi's own default keybindings also use ctrl+q to queue a follow-up message.
 If the two conflict there, change pi's binding in its keybindings file.
@@ -160,12 +162,12 @@ Claude Code settings files. Merge this into the existing object:
 }
 ```
 
-The scopes are not equal:
+The scopes aren't equal:
 
 - **User scope** (`~/.claude/settings.json`) and **managed settings** can
   set any mode.
 - **Project scope** (`.claude/settings.json` and `.claude/settings.local.json`)
-  can set `default`, `acceptEdits`, `plan`, or `dontAsk`. It cannot set
+  can set `default`, `acceptEdits`, `plan`, or `dontAsk`. It can't set
   `auto` or `bypassPermissions`; a checked-in file must not be able to turn
   off approvals for whoever clones it.
 - A `defaultMode` in `~/.onecode/settings.json` has no effect.
@@ -198,7 +200,7 @@ and these choices:
 - **No, tell the agent what to do differently.** Deny it, with an optional
   note that is passed to the model as the reason.
 
-The "don't ask again" option is not offered for protected paths, for writes
+The "don't ask again" option isn't offered for protected paths, for writes
 that the auto-mode safety floor caught, or in auto mode. Session grants never
 apply in auto mode and are cleared when the session ends.
 
@@ -226,7 +228,7 @@ check and always goes to the classifier.
 ## Protected paths
 
 Writes to these paths are never approved automatically in any mode other
-than bypass, and allow rules do not cover them.
+than bypass, and allow rules don't cover them.
 
 Protected directories, including everything inside them:
 
@@ -300,11 +302,11 @@ shows the plan. Nothing runs until you choose. The choices are:
 5. **Keep planning.** No mode change; the model refines the plan file.
 
 The initial highlight is the option that restores your previous mode, or
-manual mode when that is not offered. It never lands on a more permissive
+manual mode when that isn't offered. It never lands on a more permissive
 option by default. Press the number of a choice to pick it directly, or
 **Esc** to keep planning.
 
-In a non-interactive run there is no one to approve, so `exit_plan_mode`
+In a non-interactive run there's no one to approve, so `exit_plan_mode`
 refuses and the session stays in plan mode with the plan on disk.
 
 ## Auto mode
@@ -317,20 +319,20 @@ classifier.
 
 - Actions a deterministic analysis proves safe. Read-only shell commands
   inside the working directory are the common case. This analysis can only
-  ever conclude "safe"; anything it cannot parse or recognize goes to the
+  ever conclude "safe"; anything it can't parse or recognize goes to the
   classifier rather than through.
 - Edits and writes to files inside the project that are not credential
   files, not protected paths, and not files that run code on their own
   (build wrappers, CI workflows, editor auto-run configuration).
 - Deleting or resetting files inside the project **when git can recover
   them**. A tracked, committed file can be restored, so removing it is
-  approved. An untracked or modified file cannot, so removing it goes to
+  approved. An untracked or modified file can't, so removing it goes to
   the classifier. Claude Code trusts the whole project directory here; One
   Code checks recoverability first.
 
 ### What goes to the classifier
 
-Everything else: destructive commands git cannot undo, anything that
+Everything else: destructive commands git can't undo, anything that
 reaches outside the project, network-affecting commands, writes to
 protected paths, and reads outside the working directory.
 
@@ -342,21 +344,21 @@ The classifier is Claude Code's two-stage ruleset, embedded verbatim:
    stated intent and the allow list, and either approves or blocks with a
    named rule.
 
-Verdicts are checked before they are acted on. A block must cite a real
+Verdicts are checked before they're acted on. A block must cite a real
 rule from the ruleset. An approval based on intent must quote your own
-words from the conversation. A classifier that cannot be reached, times
-out, or returns something unparseable blocks the action; a gate that cannot
+words from the conversation. A classifier that can't be reached, times
+out, or returns something unparseable blocks the action; a gate that can't
 consult its classifier approves nothing.
 
 A blocked action is reported to the model with the reason so it can choose
-a safer route. You are not prompted per action while auto mode runs. After
+a safer route. You're not prompted per action while auto mode runs. After
 repeated blocks in a row, auto mode pauses and the next action prompts you;
 approving it resumes auto mode.
 
 Allow rules that are broad enough to pre-approve arbitrary execution, such
 as `Bash(*)`, a wildcarded interpreter, or a rule that allows delegation to
-subagents, are suspended in auto mode so they cannot bypass the classifier.
-Session grants from the approval prompt do not apply in auto mode either.
+subagents, are suspended in auto mode so they can't bypass the classifier.
+Session grants from the approval prompt don't apply in auto mode either.
 
 ### The classifier model
 
@@ -427,13 +429,13 @@ One Code's security model is the permission gate plus auto mode, not an
 assumption that the model behaves. Read these facts before you leave a
 session unattended:
 
-- **There is no operating-system sandbox.** The gate decides whether a
+- **There's no operating-system sandbox.** The gate decides whether a
   command runs; nothing constrains what an approved command can touch. For
   an OS-level wall, run One Code inside a container. The gate and the
   container work together.
 - **Bypass mode bypasses everything**, including protected paths. Claude
   Code keeps its protected-path checks active even under
-  `--dangerously-skip-permissions`; One Code does not.
+  `--dangerously-skip-permissions`; One Code doesn't.
 - **Auto mode is the default without a first-run consent step**, and
   without the OS sandbox Claude Code pairs its own auto default with.
 - **A weak classifier is a weaker boundary.** Automatic selection applies a

package/docs/guide/providers-and-models.md

@@ -1,5 +1,7 @@
 # Providers and models
 
+[← One Code user guide](README.md)
+
 One Code talks to each model provider natively, so you choose the provider
 and the model, and you can change either one during a session. This page
 covers connecting a provider, storing a key, switching models, how One Code
@@ -31,8 +33,8 @@ Two providers hand out free models you can try at no cost:
   a key, or sign in from inside One Code with no key copying. Free models
   carry a `:free` suffix, such as `nvidia/nemotron-3-ultra-550b-a55b:free`.
 
-Credentials are stored by pi in its agent directory (`~/.onecode/agent/`
-under the bundled app). `/logout` removes them.
+pi stores credentials in its agent directory (`~/.onecode/agent/` under
+the bundled app). `/logout` removes them.
 
 ## Store keys as environment variables
 
@@ -100,10 +102,10 @@ otherwise to the matching class within your provider (`haiku` the cheapest
 capable model, `sonnet` the cheapest Sonnet-class model, `opus` and `fable`
 your main model). They never switch providers.
 
-Capability is judged by tier (see the next section). Models are excluded
-when they cannot call tools, have no price, or are a generation behind: a
-model released more than a year after its vendor's newest is demoted one
-tier, and one more than two years behind is never picked automatically.
+Capability is judged by tier (see the next section). One Code excludes
+models that can't call tools, have no price, or are a generation behind: a
+model released more than a year after its vendor's newest drops one tier,
+and one more than two years behind never gets picked automatically.
 Provider aliases such as `:free` or `:online` variants are skipped.
 
 ### Measured selection with Artificial Analysis
@@ -148,8 +150,8 @@ the system prompt to match:
 | Cheap | Haiku-class models and comparable "flash", "mini", or "small" models. | The verbose prompt Claude Code gives Haiku. |
 | Tiny | Sub-Haiku models. | The verbose prompt plus extra scaffolding and the `grep`, `find`, and `ls` tools. |
 
-The tier is derived from the model's name, release date, and price. You do
-not configure it; set `CC_PROMPT_TIER` to force one when you want to
+The tier is derived from the model's name, release date, and price. You
+don't configure it; set `CC_PROMPT_TIER` to force one when you want to
 experiment. `/doctor report` shows the tier in use.
 
 ## Web search on providers without a search API
@@ -161,7 +163,7 @@ API, in this order:
 
 1. **Brave Search**, when `BRAVE_SEARCH_API_KEY` is set.
 2. **Tavily**, when `TAVILY_API_KEY` is set.
-3. **Exa's free keyless endpoint**, when neither key is set. It is
+3. **Exa's free keyless endpoint**, when neither key is set. It's
    rate-limited and best-effort, so One Code warns you the first time a
    session uses it and labels every result that came from it.
 
@@ -187,7 +189,7 @@ so. Web fetch works on every provider; it never depends on a search API.
 - Some models reject request options others accept (a temperature, a
   reasoning setting). One Code sends minimal options to its side calls for
   this reason, and a side call that still fails does so loudly: a
-  classifier that cannot answer blocks the action; a reader that fails
+  classifier that can't answer blocks the action; a reader that fails
   returns the raw page.
 - Interactive sessions request the provider's extended prompt cache (one
   hour on Anthropic). Subagents and one-shot runs use the short default.

package/docs/guide/reference.md

@@ -1,5 +1,7 @@
 # Command and keyboard reference
 
+[← One Code user guide](README.md)
+
 A lookup for every slash command, keyboard shortcut, command-line flag,
 environment variable, and file location. Each entry points to the page
 that explains it.
@@ -122,7 +124,7 @@ Rebind keys in pi's keybindings file; see pi's documentation.
 ## Command-line flags
 
 `onecode` forwards every flag to pi except `--version` and `doctor`. On the
-extension installation, use `pi` in place of `onecode`.
+extension install, use `pi` in place of `onecode`.
 
 | Flag | What it does |
 |---|---|
@@ -157,7 +159,7 @@ Set these before launching.
 |---|---|
 | `ONECODE_STATE_DIR` | Where One Code keeps its state (default `~/.onecode`). Independent of pi's agent directory. |
 | `ONECODE_NO_UPDATE_CHECK=1` | Skip the daily update check. |
-| `ONECODE_DEBUG=1` | Report when a pi-internal patch in the bundled app did not apply. |
+| `ONECODE_DEBUG=1` | Report when a pi-internal patch in the bundled app didn't apply. |
 | `AA_API_KEY` | Artificial Analysis key for measured model selection. |
 | `BRAVE_SEARCH_API_KEY`, `TAVILY_API_KEY` | Web-search fallback keys. |
 

package/docs/guide/sessions-and-context.md

@@ -1,5 +1,7 @@
 # Sessions and context
 
+[← One Code user guide](README.md)
+
 This page covers what One Code puts into the model's context, how it keeps
 long sessions within the context window, what it remembers between
 sessions, and how to continue or branch a session.
@@ -82,7 +84,7 @@ full transcript if it needs a detail.
 Run `/compact` to compact at any time; you can pass instructions about what
 the summary should focus on. Compaction that happens because the context is
 full is more expensive than a manual or threshold compaction, because it
-cannot reuse the cached prefix of the conversation.
+can't reuse the cached prefix of the conversation.
 
 Set `CC_COMPACTION=0` to use pi's own summary instead.
 
@@ -107,7 +109,7 @@ turn it off.
 
 Interactive sessions ask the provider for an extended cache lifetime (one
 hour on Anthropic; provider-dependent elsewhere), so a pause between turns
-does not re-send the whole conversation. Subagents, workflow agents, and
+doesn't re-send the whole conversation. Subagents, workflow agents, and
 `-p` or `--mode json` runs use the provider's short default. Set
 `PI_CACHE_RETENTION` yourself to take over the choice. The footer shows the
 cache-hit rate of the latest turn.
@@ -121,7 +123,7 @@ Each session gets a scratchpad directory under the system temp directory,
 named by project and session. The model is told to use it for temporary
 files instead of `/tmp`; writes there need no approval.
 
-Tool output larger than 50 KB is not truncated. It is written to a file
+Tool output larger than 50 KB isn't truncated. It's written to a file
 under the session directory, and the model receives the path, the size,
 and a 2 KB preview in a `<persisted-output>` block, so it can read the part
 it needs.

package/docs/guide/skills-plugins-and-mcp.md

@@ -1,5 +1,7 @@
 # Skills, plugins, and MCP
 
+[← One Code user guide](README.md)
+
 One Code runs Agent Skills, Claude Code plugins, and MCP servers from your
 existing configuration. This page covers using each and the panels that
 manage them.
@@ -23,7 +25,7 @@ command, as in Claude Code: `/simplify`, `/code-review`, or any skill from
 arguments. Plugin skills keep their plugin prefix and are run as
 `/skill:<plugin>:<name>`. pi's `/skill:<name>` form works for every skill.
 
-A skill's slash command is not created when the name is already taken by a
+A skill's slash command isn't created when the name is already taken by a
 built-in command, a `.claude/commands/` template, or another skill.
 
 ### Manage skills
@@ -57,7 +59,7 @@ A skill of the same name in your own `.claude/skills/` takes precedence.
 ### Skills not bundled
 
 The bundle omits the Claude Code skills that depend on services One Code
-does not have:
+doesn't have:
 
 | Group | Skills omitted |
 |---|---|
@@ -113,7 +115,7 @@ servers, agents, and hooks load on the next session, and the panel says so
 when you close it.
 
 Marketplace sources are git repositories and local paths. Version pinning,
-npm or pip sources, and dependency resolution are not implemented.
+npm or pip sources, and dependency resolution aren't implemented.
 
 ## MCP servers
 
@@ -144,7 +146,7 @@ appears as disabled in `/mcp`; choosing Enable there approves it.
 Claude Code's `enabledMcpjsonServers`, `disabledMcpjsonServers`, and
 `enableAllProjectMcpServers` settings are honored from
 `~/.claude/settings.json`, and from `.claude/settings.local.json` when that
-file is not tracked by git. They are never honored from a checked-in
+file isn't tracked by git. They are never honored from a checked-in
 `.claude/settings.json`, which would let a repository approve its own
 servers.
 
@@ -154,7 +156,7 @@ stderr.
 ### Use MCP tools
 
 Each server's tools appear to the model as `mcp__<server>__<tool>` and load
-on demand, so a server with many tools does not bloat the prompt. Servers
+on demand, so a server with many tools doesn't bloat the prompt. Servers
 also expose resources, which the model can list and read.
 
 A permission rule naming `mcp__<server>` covers every tool of that server.

package/docs/guide/subagents-and-workflows.md

@@ -1,5 +1,7 @@
 # Subagents and workflows
 
+[← One Code user guide](README.md)
+
 One Code delegates work in two ways: subagents for tasks that deserve their
 own context window, and `ultracode` workflows for fanning a large job out
 across many agents at once.
@@ -33,7 +35,7 @@ the `explore` agent". What happens next:
 - **The run starts in the background.** The model receives a task id at
   once and keeps working. The subagent's report arrives as a notification
   when it finishes, mid-turn if the model is still busy, or as a new turn
-  if it is idle. In a `-p` or `--mode json` run, the subagent runs to
+  if it's idle. In a `-p` or `--mode json` run, the subagent runs to
   completion instead and the report is returned inline.
 - **You can keep talking to the model** while agents run.
 - **Subagents go through your permission gate.** A subagent's tool calls
@@ -47,14 +49,14 @@ the `explore` agent". What happens next:
 Two options change how a subagent runs:
 
 - **Fork.** A forked subagent inherits the whole conversation so far, for a
-  task that needs everything you have built up. Forks run on the main
+  task that needs everything you've built up. Forks run on the main
   model and can only be started from the main conversation. Depth is
   limited: the main conversation can start a subagent, and that subagent
   one more, but no further.
 - **Worktree isolation.** The subagent gets its own git worktree, branched
   from `HEAD`, so it can edit files without colliding with your working
   tree or other agents. A worktree the agent left unchanged is removed;
-  otherwise it is kept and its path reported.
+  otherwise it's kept and its path reported.
 
 ### Choose the subagent model
 
@@ -90,7 +92,7 @@ agent.
 ### Follow agents live
 
 While agents run, the panel below the editor shows a tree: `main` first,
-then each agent with its type, what it is doing right now ("Reading
+then each agent with its type, what it's doing right now ("Reading
 src/index.ts", "Running a command"), its elapsed time, and its token count.
 Nested agents appear under their parent. A finished agent stays for a few
 seconds.
@@ -125,23 +127,23 @@ JavaScript script that fans the work out across many agents in parallel,
 then runs it with the `workflow` tool.
 
 The keyword arms the turn it appears in. A message you queue while the
-model is still working does not arm the next turn. For a longer stretch of
+model is still working doesn't arm the next turn. For a longer stretch of
 this kind of work, turn the mode on with `/effort ultracode`: it sets the
 reasoning effort to `xhigh` and keeps workflow orchestration armed until
-you change the effort again. The footer shows `✦ ultracode` while it is
+you change the effort again. The footer shows `✦ ultracode` while it's
 armed.
 
 ### How a workflow runs
 
-- The script runs in a separate thread, so a runaway script cannot freeze
+- The script runs in a separate thread, so a runaway script can't freeze
   the interface. A script that stops making progress is stopped after a
   few seconds; a run is capped at 30 minutes.
 - The run goes to the background and the model gets a run id. Progress
   shows in a strip below the editor (**↓** to focus it, **Enter** to open,
   **x** to stop) and in `/workflows`.
 - Every completed agent call is journaled. Re-running a workflow with
-  `resumeFromRunId` replays the calls whose inputs did not change at no
-  cost and runs only what differs. A background run does not survive the
+  `resumeFromRunId` replays the calls whose inputs didn't change at no
+  cost and runs only what differs. A background run doesn't survive the
   end of a session, but its journal does.
 - A script can carry an output-token target. Once the target is reached,
   new and queued agent calls stop; agents already running finish and can
@@ -183,11 +185,11 @@ the current run's script there.
 `/effort` sets how much reasoning the model spends: `off`, `minimal`,
 `low`, `medium`, `high`, `xhigh`, `max`, or `ultracode`. A bare `/effort`
 opens a slider (**←** and **→** or **h** and **l** move, **Enter** confirms).
-Levels the current model does not support are skipped. **shift+tab** cycles
+Levels the current model doesn't support are skipped. **shift+tab** cycles
 the plain levels; cycling away from `xhigh` while ultracode is armed turns
 ultracode off.
 
 Changing the effort re-caches the conversation, so the next request costs
-more than usual. `/effort` does not save the level across restarts; to
+more than usual. `/effort` doesn't save the level across restarts; to
 save one, open pi's `/thinking` picker and press **ctrl+s**, or pass
 `--thinking <level>` at launch.

package/docs/guide/tasks-and-background-work.md

@@ -1,5 +1,7 @@
 # Tasks and background work
 
+[← One Code user guide](README.md)
+
 One Code keeps long-running work out of the model's way. This page covers
 the structured task list, background shells, monitors, scheduled
 wake-ups, and how the results of background work reach the model.
@@ -22,8 +24,8 @@ summary line and up to 12 tasks: `✔` for completed, `◼` for in progress,
 | `/tasks show` | Shows it again. |
 
 The list is stored inside the session, so it survives a resume and follows
-the branch you are on in `/tree`. If the model has not touched the list for
-a while during a long task, it is reminded that the list exists.
+the branch you're on in `/tree`. If the model hasn't touched the list for
+a while during a long task, it's reminded that the list exists.
 
 ## Background shells
 
@@ -55,14 +57,14 @@ session is told which ones.
 The `monitor` tool watches a long-running command, or a WebSocket URL, and
 turns each line of output (or each message) into an event. Events are
 batched and delivered to the model as notifications: at most once a second
-while the model is idle, once every ten seconds while it is working, so a
-noisy process does not flood the conversation.
+while the model is idle, once every ten seconds while it's working, so a
+noisy process doesn't flood the conversation.
 
 A monitor runs until its command exits or its timeout passes (five minutes
 by default, one hour at most), or for the whole session when started as
 persistent. The model can stop it with `task_stop`.
 
-A monitor is not auto-approved, because it runs a shell command; the
+A monitor isn't auto-approved, because it runs a shell command; the
 permission gate treats it like `bash`.
 
 ## Scheduled wake-ups and loops
@@ -77,7 +79,7 @@ permission gate treats it like `bash`.
 - **Self-paced.** `/loop watch the CI run` with no interval lets the model
   choose when to check next. It uses the `schedule_wakeup` tool, which
   schedules one wake-up at a time between one minute and one hour ahead.
-  The model is told to pick a delay that matches what it is waiting for,
+  The model is told to pick a delay that matches what it's waiting for,
   and to stop the loop when the task is done.
 
 `/loop status` (or a bare `/loop`) reports the current loop. `/loop stop`
@@ -100,7 +102,7 @@ Background work reports back through notifications:
   merged into one message.
 - After you interrupt a turn, notifications are held and attached to your
   next prompt instead of starting a turn on their own.
-- Each notification is framed as an automated event, so the model does not
+- Each notification is framed as an automated event, so the model doesn't
   mistake it for something you said or approved.
 
 ## Non-interactive runs
@@ -108,4 +110,4 @@ Background work reports back through notifications:
 In `-p` and `--mode json` runs nothing can run in the background, because
 the process exits when the turn settles. Background shells, monitors,
 subagents, and workflows run to completion and return their output
-directly. `/loop` and `schedule_wakeup` do not fire.
+directly. `/loop` and `schedule_wakeup` don't fire.

package/docs/guide/terminal-interface.md

@@ -1,5 +1,7 @@
 # The terminal interface
 
+[← One Code user guide](README.md)
+
 This page describes what you see on screen and how to move around it: the
 banner, the status line, the working indicator, the panels below the
 editor, the dialogs, and the themes.
@@ -70,8 +72,8 @@ Set `CC_FOOTER=0` to keep pi's footer.
 ## The panel below the editor
 
 One panel below the editor holds the background-shell manager and the
-live subagent tree. It appears when there is something to show and hides
-when there is not.
+live subagent tree. It appears when there's something to show and hides
+when there isn't.
 
 - Press **↓** from an empty editor to focus it. If background shells exist,
   the first **↓** lands on the shells chip; a second **↓** moves to the
@@ -85,7 +87,7 @@ when there is not.
   **Enter** closes the view.
 
 The panel's own footer names the keys that apply at each stage. Mouse-wheel
-scrolling is deliberately not enabled in the transcript view, because
+scrolling deliberately isn't enabled in the transcript view, because
 turning on mouse reporting would take over the terminal's native scrolling
 and text selection for the whole session.
 
@@ -132,7 +134,7 @@ and [Plan mode](permissions-modes-and-auto-mode.md#plan-mode).
 
 **ctrl+c** closes any panel.
 
-PgUp and PgDn do not reach these panels in full-screen mode, because pi uses
+PgUp and PgDn don't reach these panels in full-screen mode, because pi uses
 them for its own scrollback; use the keys the panel's footer names.
 
 ## Full-screen mode

package/docs/guide/tools.md

@@ -1,6 +1,8 @@
 # Tools
 
-The model works by calling tools. You do not type tool names; you describe
+[← One Code user guide](README.md)
+
+The model works by calling tools. You don't type tool names; you describe
 the task and the model chooses. This page lists every tool One Code gives
 the model, what each does, what you see when it runs, and how Claude Code's
 tool names map onto them.
@@ -55,7 +57,7 @@ Some command shapes are refused before they run, with a message that steers
 the model to a better route:
 
 - A foreground command that starts with `sleep`, or a polling loop that
-  sleeps, when the wait is not provably short. The model is told to use
+  sleeps, when the wait isn't provably short. The model is told to use
   `run_in_background` or `monitor` instead.
 - A command that would orphan a process (`nohup`, `setsid`, or a trailing
   `&` with no `wait`).
@@ -131,7 +133,7 @@ deferred until needed. `list_mcp_resources`, `read_mcp_resource`, and
 
 `tool_search` loads deferred tools. The model passes exact names
 (`select:monitor,task_output`), a required term (`+notebook`), or free
-keywords. If the model calls a tool it has not loaded yet, the call fails
+keywords. If the model calls a tool it hasn't loaded yet, the call fails
 and the model is steered to `tool_search`.
 
 ## Behavior in non-interactive runs

package/docs/guide/troubleshooting.md

@@ -1,5 +1,7 @@
 # Troubleshooting
 
+[← One Code user guide](README.md)
+
 Symptoms you might hit, what causes them, and what to do.
 
 ## Start with the doctor
@@ -38,9 +40,9 @@ pins pi itself.
 pi it runs on are out of step. On the bundled app, reinstall it. On your own
 pi, run `pi update --extensions`.
 
-**The stock pi first-run wizard did not appear.** The bundled app seeds
+**The stock pi first-run wizard didn't appear.** The bundled app seeds
 pi's settings with the One Code theme, quiet startup, and full-screen mode
-on first run, so there is nothing to ask.
+on first run, so there's nothing to ask.
 
 ## Permissions
 
@@ -57,7 +59,7 @@ check `/permissions`: an `ask` rule prompts in every mode.
 
 **An allow rule I wrote has no effect in auto mode.** Broad execution rules
 (`Bash(*)`, wildcarded interpreters, delegation rules) are suspended in
-auto mode so they cannot bypass the classifier. Session grants from the
+auto mode so they can't bypass the classifier. Session grants from the
 approval prompt are also ignored there. Narrow the rule or switch to
 accept-edits or manual mode.
 
@@ -66,7 +68,7 @@ may not select auto or bypass mode. Set it in `~/.claude/settings.json`
 or pass `--permission-mode auto`.
 
 **`defaultMode` in `~/.onecode/settings.json` does nothing.** The
-permission loader does not read that key from One Code's file. Use a Claude
+permission loader doesn't read that key from One Code's file. Use a Claude
 Code settings file or the flag.
 
 **The model is denied a write to `.claude/settings.json`.** The auto-mode
@@ -80,12 +82,12 @@ allow rules, or use auto mode with a provider that can run the classifier.
 ## Auto-mode classifier
 
 **Actions are blocked with a message about the classifier being
-unavailable.** The classifier model could not be reached or returned
+unavailable.** The classifier model couldn't be reached or returned
 nothing usable; the gate fails closed. Check `/auto-mode config` for the
 model in use, and `/doctor report` for provider credentials. Set
 `CC_AUTO_MODE_DEBUG=1` to see each verdict on stderr.
 
-**The classifier approves or blocks something it should not.** Choose a
+**The classifier approves or blocks something it shouldn't.** Choose a
 stronger classifier with `/auto-mode model <provider/model-id>`. A
 Haiku-class classifier is a measurably weaker boundary than a Sonnet-class
 one.
@@ -122,7 +124,7 @@ to a rate-limited endpoint. Set `BRAVE_SEARCH_API_KEY` or
 `/doctor report` for install hints.
 
 **TypeScript diagnostics fail with a message about `lib/tsserver.js`.**
-TypeScript 7's native compiler does not ship that file, and
+TypeScript 7's native compiler doesn't ship that file, and
 `typescript-language-server` needs it. Install a TypeScript 5.x development
 dependency in the project.
 
@@ -139,7 +141,7 @@ Authenticate. Tokens are stored under `~/.onecode/mcp-auth/`.
 
 ## Hooks
 
-**A project's hooks do not run.** They need one-time approval at startup.
+**A project's hooks don't run.** They need one-time approval at startup.
 Restart the session and accept, or check
 `~/.onecode/hooks/project-approvals.json`.
 
@@ -152,10 +154,10 @@ Restart the session and accept, or check
 **My background shells are gone after `/clear`.** Background work ends
 with the session. The new session lists what was stopped.
 
-**A resumed session is in a different permission mode.** Modes are not
+**A resumed session is in a different permission mode.** Modes aren't
 saved with the session. Pass `--permission-mode` or set a default.
 
-**The `/effort` level reset after a restart.** `/effort` does not save the
+**The `/effort` level reset after a restart.** `/effort` doesn't save the
 level. Open pi's `/thinking` picker and press **ctrl+s** to save a startup
 default, or pass `--thinking <level>` at launch.
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "one-code-extension",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "One Code as a pi package — the Claude Code experience on your own pi install: ported system prompt, Claude-Code-format permissions, .claude/ compatibility, ToolSearch-style deferred tools, and system-reminder steering. For the bundled app, install `@one-ai/one-code` instead.",
 	"keywords": [
 		"pi",