orc-ai 0.1.37 → 0.1.41

package/README.md

@@ -61,6 +61,8 @@ On first launch the app sets everything up:
 
 The builds are unsigned: on macOS right-click the app and choose Open the first time, on Windows choose "More info" then "Run anyway".
 
+The sidebar shows the saved execution host, for example `Connected (lab)` or `Connected (local)`. Switching hosts applies to new actions immediately. For a full restart, use **Settings → ORC server → Restart ORC server**; it keeps settings and reconnects the dashboard automatically. Restart closes active terminals and may interrupt running work. Host changes never trigger a restart automatically.
+
 <details>
 <summary>Headless / CLI-only install (servers, Docker, CI)</summary>
 
@@ -122,6 +124,38 @@ orc task list
 
 Open `http://localhost:7700` to use the web dashboard - task board, kanban, flow runs, jobs, memories, sessions, knowledge, and a live chat panel. The same server hosts both the REST API and the prebuilt React SPA, so there is no separate command to run for the UI.
 
+Chat uses the shared agent runtime: Claude through its SDK, Codex through its native
+CLI, and other agents through ACPX. Choose a model from the composer; configure
+model choices, conversation instructions, the ORC MCP connection and automatic
+actions in **Settings → Chat**. Defaults are stored in `preferences.chat` in ORC's
+JSON configuration and apply to new conversations on every device. The model
+dialog shows the current conversation's setup. Claude appends the instructions
+to its coding system prompt; Codex and ACPX receive them as turn instructions.
+Agent and workspace instructions may also apply.
+
+Automatic actions default off: Claude can request approval in chat, Codex uses a
+read-only sandbox, and ACPX follows its agent's native permission policy. Enabling
+automatic actions lets Claude bypass permission prompts and Codex write inside
+its workspace; ORC rules remain enforced. The ORC MCP option adds an authenticated
+connection for Claude and Codex without exposing credentials to the browser.
+Host configuration can include additional MCP servers; choosing host configuration
+does not disable those servers. Other ACPX agents require host configuration.
+
+Use the history icon to continue a saved chat or an ended Claude/Codex coding
+session. Synced sessions use the existing verified repository/commit handoff;
+provide missing checkout details before importing. Native history stays with the
+agent, while chat displays up to 100 recent imported turns. An active source session
+must end before chat resumes it. Resume failures never trigger a fresh session.
+New chats use the API working directory locally or the selected SSH host's home;
+resumed chats retain their execution host and folder. New conversation keeps the
+previous chat in history.
+
+Responses show provider-supplied text, collapsible thinking summaries and tool
+input/results as they arrive, with a responding indicator during quiet periods.
+Some providers emit complete blocks rather than individual tokens. Conversation
+messages and activity are saved in the ORC database. Full-screen mode preserves
+the conversation; phones and tablets use a full-screen chat sheet automatically.
+
 > [!TIP]
 > The database is created automatically at `~/.orc/orc.db` on first run. No setup needed.
 
@@ -393,6 +427,8 @@ Enable the task loop in `~/.orc/config.json`:
 
 Projects group tasks, memories, and jobs. Set an active project and all commands auto-scope:
 
+Projects can also store an optional Git remote URL in the create/edit dialog or through `--git-remote-url`. HTTPS and SSH addresses are supported without embedded credentials. The address is project metadata; setting it does not clone a repository or change a checkout's remote. Clear it in the editor, send `git_remote_url: null` through the API, or use `orc project update my-app --clear-git-remote-url`.
+
 ```bash
 orc project add my-app -d "Main application"
 orc project use my-app       # set active
@@ -698,7 +734,7 @@ orc skill validate ./my-workflow
 orc skill export my-workflow ./exported/my-workflow
 ```
 
-Import public GitHub skills from **Skills → Import from GitHub**. Paste a repository URL, `owner/repo`, a GitHub skill-folder URL, or a `https://skills.sh/owner/repo/skill` link, discover the skills, then select which to import. ORC copies each complete folder at the displayed commit, including nested documentation, scripts and binary assets. Existing names are never overwritten by an import. Select up to 16 skills per import (64 MiB total).
+Import GitHub skills from **Skills → Import from GitHub**. Paste a repository URL, `owner/repo`, a GitHub skill-folder URL, or a `https://skills.sh/owner/repo/skill` link, discover the skills, then select which to import. Private repositories use `gh` credentials on the configured execution host (local by default, remote when `ssh.host` is set), falling back to `ORC_GITHUB_TOKEN` / `github.token` on the ORC server; credentials need access to the repository. Without credentials, public repositories still work. ORC copies each complete folder at the displayed commit, including nested documentation, scripts and binary assets. Existing names are never overwritten by an import. Select up to 16 skills per import (64 MiB total).
 
 ```bash
 orc skill import vercel-labs/agent-skills --list