Dark-Alex-17/coyote
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: renamed Sharing Configurations to Bundles

Dark-Alex-17
2026-08-27 16:12:18 -06:00
parent bbbdc74fb6
commit 8fc7fea492
7 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Sharing-Configurations.md → Bundles.md
Custom-Tools.md
+2 -2
@@ -33,7 +33,7 @@ it works on your host.
Two layouts work:
**Per-tool mixin:** Co-located with the tool itself, applies whenever any sandbox is launched. Use this when the tool
is meaningful as a portable unit you'd share via [Sharing Configurations](Sharing-Configurations):
is meaningful as a portable unit you'd share via [Bundles](Bundles):
```
<coyote-config-dir>/functions/<your-tool-dir>/
@@ -100,7 +100,7 @@ path table and the [official sbx mixin reference](https://docs.docker.com/ai/san
- **Mixin install steps run as UID 1000 (the `agent` user) with passwordless sudo.** Don't assume root home paths;
use `~/` or explicit `/home/agent/` if you need a known location.
- **When sharing a custom tool, ship its `sbx-mixin.yaml` alongside it.** Without it, recipients will hit silent
sandbox failures with no obvious cause. See [Sharing Configurations: Sandbox Implications](Sharing-Configurations#sandbox-implications)
sandbox failures with no obvious cause. See [Bundles: Sandbox Implications](Bundles#sandbox-implications)
for the security implications of a shared mixin.
## Environment Variables
Home.md
+2 -2
@@ -15,7 +15,7 @@ Coyote comes ready to use with built-in agents, roles, macros, and tools, so you
from scratch. When you want to extend it, entire bundles of agents, roles, macros, tools, MCP servers, and other configurations
can be installed directly from any Git repository.
See [Sharing Configurations](https://github.com/Dark-Alex-17/coyote/wiki/Sharing-Configurations) to learn how to create, install,
See [Bundles](https://github.com/Dark-Alex-17/coyote/wiki/Bundles) to learn how to create, install,
and share Coyote bundles.
![Agent example](./images/agents/sql.gif)
@@ -28,7 +28,7 @@ Coming from [AIChat](https://github.com/sigoden/aichat)? Follow the [migration g
* [AIChat Migration Guide](AIChat-Migration): Coming from AIChat? Follow the migration guide to get started.
* [Installation](Installation): Install Coyote
* [Getting Started](Getting-Started): Get started with Coyote by doing first-run setup steps, and learn the basics.
* [Sharing Configurations](Sharing-Configurations): Install bundles of agents, roles, macros, tools, and MCP servers from any git repo, and share your own. Bundles are Coyote's equivalent of plugins in other CLI agents.
* [Bundles](Bundles): Install bundles of agents, roles, macros, tools, and MCP servers from any git repo, and share your own. Bundles are Coyote's equivalent of plugins in other CLI agents.
* [REPL](REPL): Interactive Read-Eval-Print Loop for conversational interactions with LLMs and Coyote.
* [Custom REPL Prompt](REPL-Prompt): Customize the REPL prompt to provide useful contextual information.
* [Vault](Vault): Securely store and manage sensitive information such as API keys and credentials.
REPL.md
+2 -2
@@ -454,7 +454,7 @@ The `.list` command lists the assets of a given kind, making them discoverable w
| `.list agents` | List installed agents, with their descriptions when available |
| `.list rags` | List all RAGs |
| `.list macros` | List all macros |
| `.list bundles` | List installed bundles with their source, version, ref pin, and drift status (see [Sharing Configurations](Sharing-Configurations)) |
| `.list bundles` | List installed bundles with their source, version, ref pin, and drift status (see [Bundles](Bundles)) |
| `.list skills` | List skills available in this context, with descriptions and a `(loaded)` marker for active skills |
| `.list prompts` | List MCP prompts across all enabled servers (live listing), with each prompt's server, description, and arguments |
| `.list tools` | List the tools that can be enabled/disabled via `.tool [enable\|disable] <name>` (excludes internal tools; in an agent context, lists the agent's tool pool) |
@@ -506,7 +506,7 @@ This is the primary mechanism for sharing and reusing Coyote configurations; an
The CLI equivalent is `coyote --install <source-or-name>` (with `--git-host`, `--filter`, and `--install-force`
accepting the same values). Use `.list bundles` to see what's installed and `.uninstall <name>` to remove a bundle.
See [Sharing Configurations](Sharing-Configurations) for the expected repo layout, conflict resolution, secret handling,
See [Bundles](Bundles) for the expected repo layout, conflict resolution, secret handling,
and the [coyote-bundle-template](https://github.com/Dark-Alex-17/coyote-bundle-template) starter you can fork.
## `.uninstall` - Uninstall a bundle
Sandboxes.md
+2 -2
@@ -132,7 +132,7 @@ Applying 2 sbx mixin(s):
If zero mixins were discovered, you'll see `No sbx mixins discovered.` in the log (no terminal noise).
Skim this log on first launch and after installing any [shared configuration bundle](Sharing-Configurations). It's your
Skim this log on first launch and after installing any [shared bundle](Bundles). It's your
audit point for what each mixin grants in terms of installs and network domain allowances.
## Lifecycle: use the sbx CLI
@@ -456,7 +456,7 @@ You can list everything that's about to be applied via the [verbose mixin log](#
### Sharing mixins with others
A mixin in `<config-dir>/agents/<agent>/sbx-mixin.yaml` travels with the agent if you publish it via the [Sharing Configurations](Sharing-Configurations)
A mixin in `<config-dir>/agents/<agent>/sbx-mixin.yaml` travels with the agent if you publish it via the [Bundles](Bundles)
mechanism. See that page for the security implications. Installing a bundle that ships an `sbx-mixin.yaml` grants the
included install commands and network domains the next time you `coyote --sandbox`.
Skills.md
+3 -3
@@ -149,7 +149,7 @@ your current context with git knowledge, frontend conventions, or any other modu
| `.skill <name>` | Open the skill in `$EDITOR`. Creates a scaffolded `SKILL.md` if missing. |
| `.delete skill` | Interactive prompt to choose installed skills to delete. |
| `.install skills` | Reinstall all bundled built-in skills, overwriting existing copies after confirmation. |
| `.install <git-url> --filter skills` | Install only `skills/` from a remote repo. See [Sharing Configurations](Sharing-Configurations). |
| `.install <git-url> --filter skills` | Install only `skills/` from a remote repo. See [Bundles](Bundles). |
| `.set skills_enabled <true\|false\|null>` | Flip the master switch at runtime. Inside a session this sets the session override; otherwise it updates the global default (`null` restores the default `true`). |
| `.set enabled_skills <csv\|null>` | Replace the global default-active skill list at runtime, e.g. `.set enabled_skills git-master,ai-slop-remover`. Use `null` to clear. |
@@ -421,7 +421,7 @@ yourself are left untouched.
# Sharing Skills
Skills install via the same [Sharing Configurations](Sharing-Configurations) flow as other Coyote assets. A remote repo
Skills install via the same [Bundles](Bundles) flow as other Coyote assets. A remote repo
laid out as:
```
@@ -439,7 +439,7 @@ coyote --install <owner>/<repo>
coyote --install <owner>/<repo> --filter skills
```
See [Sharing Configurations](Sharing-Configurations) for the full layout, ref pinning, conflict resolution, and secrets
See [Bundles](Bundles) for the full layout, ref pinning, conflict resolution, and secrets
handling. Skills follow the standard per-file conflict prompts.
---
_Sidebar.md
+1 -1
@@ -2,7 +2,7 @@
- [Home](Home)
- [Installation](Installation)
- [Getting Started](Getting-Started)
- [Sharing Configurations](Sharing-Configurations)
- [Bundles](Bundles)
- [AIChat Migration](AIChat-Migration)
## Using Coyote