FerroxLabs/murage

Última actividad de origen registrada: 28 de octubre de 2026 a las 21:32

Catálogo de SkillsMP actualizado: 12 de noviembre de 2026 a las 12:52

skills recopiladas: 2253

Estrellas en GitHub: 17
Forks en GitHub: 4

Instalar con un asistente de IA

Copia este prompt en el asistente de IA que estés usando.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/FerroxLabs/murage.

README del repositorio

Archivo de origen del README: README.md

Leer el README original

Mostrar README completo

<div align="center"> <img src="brand/readme-hero-workforce-0.1.47.png" alt="Murage. You have the vision. Put an AI workforce behind it. Dark-mode team conversation, Chief of Staff and Team map." width="100%"> **You have the vision. Put an AI workforce behind it.** Brief your AI Chief of Staff. It assembles specialists, coordinates their work, and brings the results back to you, with shared tools, durable memory and you in control. *For founders, creators and operators with more ideas than hands.* [Build your first AI team →](#download) · [About](#about-murage) · [See it in action](#a-real-brief-a-working-team) · [Web & mobile](#your-workspace-on-the-device-in-your-hand) · [Memory](#memory-that-you-can-inspect-and-control) · [Telegram](#stay-in-the-conversation-from-telegram) </div> Start with the outcome: launch a product, research a market, review a codebase or build a content workflow. Murage™ brings together a **Chief of Staff, specialist teams, 2,237 skills, connected tools and durable memory** in one workspace. Use a prebuilt team or ask a capable Chief to assemble one for the job. Give agents a browser or computer where supported, follow their work, and make the decisions that need you. Work in the desktop app, continue through the responsive Web UI or PWA, or message your Chief from Telegram. **Fuigo is included, and multi-vendor choice is built in.** ## Download **[Latest release](https://github.com/FerroxLabs/murage-releases/releases/latest)** · [All releases](https://github.com/FerroxLabs/murage-releases/releases) | Platform | Installer | |---|---| | macOS · Apple Silicon | **[Download for Mac](https://github.com/FerroxLabs/murage-releases/releases/latest/download/Murage.dmg)** | | macOS · Intel | [Download for Intel Mac](https://github.com/FerroxLabs/murage-releases/releases/latest/download/Murage-intel.dmg) | | Windows · x64 | **[Download for Windows](https://github.com/FerroxLabs/murage-releases/releases/latest/download/Murage-setup.exe)** | | Ubuntu 24.04 · x64 | **[Download .deb](https://github.com/FerroxLabs/murage-releases/releases/latest/download/Murage-amd64.deb)** · [AppImage](https://github.com/FerroxLabs/murage-releases/releases/latest/download/Murage.AppImage) | Mac downloads are signed and notarized. Windows downloads are signed. See the release notes for platform verification and known limitations. [Ubuntu checksums](https://github.com/FerroxLabs/murage-releases/releases/latest/download/SHA256SUMS-ubuntu-x64.txt) are available alongside the downloads. **Fuigo is bundled. Installed desktop builds require no Node.js, npm, pnpm or separate Fuigo installation.** Your selected engine still needs its own provider login or API credentials; model access and provider charges are separate. If an official desktop build says “Fuigo CLI not found” or asks you to install Fuigo through npm, that is a bundled-engine detection or installation problem, not a normal prerequisite. Report your Murage version, operating system and installer type. Do not include API keys. ## About Murage **Everyone should have a team.** Most people with more ideas than hours have no one to hand work to, and most businesses have good people buried in busywork. Murage gives both a Chief of Staff and a team of AI agents that work on your own computer, with the AI you already use. You brief your Chief of Staff the way you would brief a person. It works out who is needed, sets up specialist bots or whole teams, hands out the work, keeps track of it and brings the results back to you. Every bot has its own role, instructions, memory, folders and tools, and nothing risky happens without your say: you choose how much each bot may do on its own, and you can see and change what it remembers. Two rules shape everything we build: - **Easy to start.** Download it, connect the AI you already have (Claude Code, Codex, Gemini, Hermes, a local model or your own API key) and tell your Chief of Staff what needs doing. - **Grows with you.** Start with one bot clearing an inbox. Grow into teams that run whole parts of a business, with routines on a schedule, shared projects, connected apps, your phone and your chat apps. AI changes every month, so Murage changes with it. New engines, tools and abilities land in each release, and the [changelog](https://murage.ai/changelog) lists every one. > "Murage grew out of the harness we already ran our own work on inside Ferrox Labs. It worked, and I wanted everyone to have it: a real team in your hands, whatever AI you use underneath." > > Sean Donahoe, founder, Ferrox Labs ## A real brief. A working team. A 14-day launch. A $3,000 budget. No paid ads. The strategist proposes priorities; the reviewer challenges the assumption that could make the plan fail. ![Actual Astra replies in a Murage shared channel: Maya proposes a launch plan and Theo challenges its riskiest assumption](docs/screenshots/murage-team-dark-0.1.47.png) *A saved, real GPT-6 Astra conversation in an isolated demo workspace, now shown in dark mode with custom demo avatars. Harbor Notes and its team identities are fictional.* ## A Chief of Staff for the whole workspace Give your team a central point of coordination. The **Chief of Staff** sits above team leads and specialists, so you can organize work across several teams instead of managing an undifferentiated list of bots. In this demo, Mira is Chief of Staff. Maya leads Launch Studio with Theo reviewing the product plan; Sofia leads Content Studio. Each team has its own group conversation. Open **Team map** to see who leads whom and where work is moving. ![Murage Team map in dark mode: Chief of Staff Mira above Content Studio and Launch Studio](docs/screenshots/murage-chief-team-map-0.1.47.png) Custom avatars, named teams and group portraits make that structure easy to recognize in the sidebar. Each agent still has its own role, instructions and model selection. ## Start with a team. Or let your Chief assemble one. You do not have to invent every role and workflow yourself. Browse **prebuilt teams** for an outcome, inspect their members and playbooks, and choose what to import. Bots can also work on their own, with their own instructions, model and task history. With a delegation-compatible engine, your Chief can use the live roster, create useful specialists when you ask for a team, and assign them work. The Chief stays your central point of contact. Nested Chief-to-lead-to-specialist delegation has a known tool-availability limitation; improvements are in development and are not part of this release. > “Build a launch team for this product. Have a strategist propose the plan, a reviewer challenge the assumptions, and a writer prepare the copy. Bring me the decisions.” ### 2,237 skills to build on The shipped skill library spans research, writing, engineering, design, operations and business workflows. Search for the task, find an existing playbook and give the right capabilities to the right agent. Team import previews show what will be added before you accept; credentials and permission grants do not travel inside a team package. ![Murage’s prebuilt team library in dark mode, with outcome-focused teams and their included playbooks](docs/screenshots/murage-prebuilt-teams-dark-0.1.47.png) ## Give your agents somewhere to work A plan becomes more useful when the agent can work with the tools and environments the task requires. | Environment | What it is for | |---|---| | **Browser** | Work with web pages through browser tools and, where available, view the interactive browser inside Murage. | | **This computer** | Use the host's screen and applications after the required platform permissions and explicit setup. | | **Local VM** | Give an agent a separate local Linux desktop in supported configurations. | | **Remote / cloud computer** | Connect a supported cloud or user-managed remote desktop environment, separate from your everyday computer. | | **Off** | Keep desktop access disabled for work that does not need it. | Choose the destination per bot. Browser, local control, VM and remote access have their own setup requirements; engine support and permissions determine which actions are available. Hosted computers can have separate costs. ## Keep the lessons. Improve the playbook. A useful process should become something your team can reuse. A correction should become context for the next attempt. Ask an agent to **`/learn`** a workflow, a source, or what you just worked through. It can distill the steps into a reusable skill, or revise an existing learned skill when you explicitly request it. Murage stages the change for review; **you approve it before it becomes active**. Combined with managed memory, this gives the team an evolving working playbook: relevant context for the current task, reusable procedures for recurring work, and corrections you can inspect and carry forward. The team can adapt its plan and specialist mix to the workload while permanent skill changes stay under your control. ## Memory that you can inspect and control **Memory belongs to Murage, independently of the engine chosen for an agent.** It is stored as durable records with source history and searchable indexes. Relevant context is selected for eligible turns; supported integrations also expose deeper memory tools. - **Recall useful context.** Search by keywords and, after the optional local-model download on supported platforms, by meaning. Bounded context keeps a growing history from becoming one ever-larger prompt. - **Keep audiences separate.** Bot, conversation, channel, team and project scopes determine what can be recalled. Private notes do not automatically become shared team knowledge. - **See where a memory came from.** Inspect source excerpts and versions. Review candidates, correct a record, or pin an important constraint. - **Share deliberately.** Approve knowledge for a different audience instead of silently pooling everything every agent knows. - **Forget and recover.** Forgetting excludes affected material from future recall. Authoritative memory is included in installation backups; derived indexes can be rebuilt. - **Bring existing notes forward.** Preview and import existing notebooks or team briefs while preserving the original files. ![Murage memory inspection showing an imported launch brief with its source and audience](docs/screenshots/murage-memory-dark-0.1.47.png) *Inspect the saved launch brief’s source and audience. This record was deliberately imported from the demo conversation and retains its unverified-import label.* **Managed memory is on (Capture and recall) for a new installation; an existing installation keeps the mode it already has.** Open **More → Team map → Manage memory** to choose Off, Capture only or Capture and recall. Local indexing does not require a paid extraction model. Optional model-based extraction is a separate, explicit setting and creates review candidates. Local storage is not the same as local-only AI processing: recalled context sent to a hosted engine is processed by that provider. Forgetting cannot retract text already sent. Local semantic retrieval (smart search) is available on Apple Silicon and Intel Macs, Windows x64 and Linux x64. Intel Macs run the same model on ONNX Runtime WebAssembly, so building the index for a large memory takes longer there; searches during a turn are not held up by it. [Read the memory guide](docs/memory.md). ## Your workspace, on the device in your hand Start at your desk. Continue from your phone, tablet or another computer. Murage's **Web UI serves the same workspace**, so you can follow conversations and work from a paired browser without installing another desktop copy. - **Responsive on mobile.** Navigation, conversations and controls adapt to smaller screens and touch input. - **Installable as a PWA.** On a supported browser with secure HTTPS access, add Murage to your home screen or install it as a standalone web app. - **Private remote access.** Enable browser access and pair your device over your own Tailscale network. The workspace is not automatically exposed to the public internet. - **One running workspace.** Agents execute on the host running Murage; your paired device connects to that host. Keep it available when you want to continue elsewhere. <p align="center"><img src="docs/screenshots/murage-mobile-dark-0.1.47.png" alt="Murage mobile navigation in dark mode, showing the Chief of Staff, team leads, custom avatars and group conversations" width="320"></p> *The same demo workspace, with its touch-friendly navigation open on a phone-sized screen.* Desktop-only administration stays on the desktop. The PWA does not turn a phone into an independent agent host, and an offline shell does not keep remote agents working without a connection. ## Stay in the conversation from Telegram Message your Chief of Staff from a **paired private Telegram chat**. Messages join the Chief's current Murage conversation, so the desktop and Telegram views stay connected to the same work. For supported ordinary tool requests, the paired owner gets **Approve once** and **Deny** buttons. For stop-line actions such as deleting outside a folder, paying or messaging someone new, there is also **Allow for this task**, which covers the same kind of action in the same place until the task ends. Richer proposal reviews stay in Murage; typing “approve” in a message does not grant permission. Set it up in **Settings → Messaging apps → Telegram** using your own bot token and a pairing code. Keep Murage running and pair again after restarting. Revoke the connection from Settings when you no longer want it active. | Service | What you can do today | |---|---| | **Telegram** | Continue the Chief’s conversation and answer supported one-time approval requests from a paired private chat. | | **Slack** | Message your Chief from one Slack direct message through your own private Slack app, and it answers there. Approvals arrive as Approve once and Deny buttons. Computer-control cards show Deny only. Slack as a connected app, where bots read and post in your workspace, is separate. | | **Discord** | Message your Chief from one Discord direct message through your own Discord bot, and it answers there. Approvals arrive as Approve once and Deny buttons. Computer-control cards show Deny only. Only your own direct messages are read. Server messages are ignored. | Telegram group routing remains future work. Telegram, Slack and Discord read only your own paired direct messages. WhatsApp follows its own groups and contacts settings. [Telegram setup and boundaries](docs/telegram.md). ## Fuigo built in. Multi-vendor by design. **Fuigo is Murage’s bundled agent harness**, with its tool and permission integration included in the shipped desktop build. You can start with it without separately installing Fuigo. The release checks cover the bundled executable and its integration; provider login and model access remain yours. Multi-vendor choice is part of the product, not an add-on. Use Fuigo, installed engines such as **Claude Code** and **Codex**, custom ACP agents, or compatible API endpoints. Choose an engine and model per agent, mix them in a team, and keep Murage-owned conversations and memory around that work. Each engine retains its supported capabilities and permission requirements. ## Connect the tools your team uses Connect tools as **connected apps** (Gmail, Slack, GitHub, Notion and many more) or through your own **MCP servers**. Search can use an engine's native capability, Murage's built-in backup search mode, or an explicitly selected Tavily, Exa or Firecrawl account. Browser and computer tools are available in supported configurations with their required permissions. Murage also includes a local MCP server for other clients to list the team, send work, read bounded transcripts and wait for results. This coordination interface does not grant those clients permission to approve actions or change credentials. **Capabilities depend on the engine and platform.** A text-only compatible endpoint can discuss and write without being able to operate tools. Connecting an account does not bypass approvals, and memory does not grant filesystem or computer access. ## Start with one useful task 1. **Install and open Murage.** On macOS, move it to Applications. On Windows, run the installer. On Ubuntu, use `sudo apt install ./Murage-amd64.deb`, or make the AppImage executable and open it. 2. **Set up an engine.** Open Settings → Engines and use the login or credentials it requires. 3. **Create an Ember or review a team.** Give it a clear role and choose its model. 4. **Send a concrete brief.** Include the outcome, constraints and what needs your approval. Add teammates to a channel when another perspective helps. 5. **Make the workspace yours.** Enable the memory mode and audiences you want. Pair the Web UI/PWA for another device, connect Telegram for messaging, or give capable agents access to Slack and other tools. ## Before you choose a setup - Reported engine errors `-32603` and unexpected exit `1073807364` remain under investigation. The reproduced Claude background-task notification bug was fixed, but that does not establish a fix for every reported engine error. - An intermittent Mac shutdown delay during credential-write drain remains a known limitation. Later signed native checks exited cleanly; the original delay and native credential persistence were not conclusively resolved. See the [release notes](https://github.com/FerroxLabs/murage-releases/releases/latest). | Area | Current boundary | |---|---| | Windows browser | See [release notes](https://github.com/FerroxLabs/murage-releases/releases/latest) for Windows verification and known limitations. | | Ubuntu desktop control | The app runs on GNOME Xorg and Wayland; local computer control is restricted to Xorg. Linux dictation and ARM64 installers are unavailable. | | Intel Mac memory | Smart search works with the bundled model, run on ONNX Runtime WebAssembly. Results match the native runtime used on other platforms. Indexing is about 4 times slower and runs in the background, so searches during a turn do not wait for it. Intel builds do not include the GEPA learning worker. | | Background work | Murage's host must remain available for routines and Telegram. This release is not an always-on hosted service. | | Memory scale | Verified for ordinary interactive use. Sustained high-throughput ingestion and continuous-search saturation tuning remain deferred. | | Cross-device memory | No automatic memory synchronization between separate installations or profiles. | ## Source code Murage is free software under the [GNU Affero General Public License v3.0 or later](LICENSE). The complete source is public at [github.com/FerroxLabs/murage](https://github.com/FerroxLabs/murage). Under section 13 of the AGPL, anyone who uses a modified Murage over a network is entitled to the source of the version they are using, and the app links to this repository from Settings, About, in the desktop app and in the browser door alike. Bundled third-party components keep their own licenses; see [NOTICE](NOTICE). ## Build from source Building needs Node.js 24+ and pnpm 10.33.0. ```sh git clone https://github.com/FerroxLabs/murage.git cd murage pnpm install --frozen-lockfile ``` Run `pnpm dev:server` and `pnpm dev` in separate terminals, then `pnpm dev:desktop` for the Electron shell. Use `pnpm typecheck` and `pnpm test` for validation. Native installer commands are `pnpm package:mac`, `pnpm package:win` and `pnpm package:linux`; packaging is separate from publication. On Linux (x64 or arm64), run `pnpm build:murage-cage` first, on the same architecture. It needs Docker running and the host packages `build-essential pkg-config libseccomp-dev binutils xz-utils` (libseccomp 2.5.5, as on Ubuntu 24.04). On Ubuntu 23.10 and later, run `pnpm cage:apparmor` once from this repository after the build to install its source-path AppArmor profile with sudo. The source launch commands build a missing cage automatically and check that it can launch; `pnpm start` also starts the server. Further guides: [custom engines](docs/custom-engines.md), [custom MCP servers](docs/custom-mcp-servers.md), [Murage MCP server](docs/mcp-server.md), [connected apps](docs/connected-apps.md), [Ubuntu](docs/linux-desktop.md), [recovery](docs/verification/installation-recovery.md), and [releasing](docs/releasing.md). ## About Ferrox Labs Murage is made by **Ferrox Labs, LLC** in Austin, Texas, founded by Sean Donahoe. We build tools that put AI to work for real people and real businesses: Murage, the Fuigo coding engine and Flux Router, our service for AI models, connected apps, voice and web search. | | | |---|---| | Website | [murage.ai](https://murage.ai) | | About us | [murage.ai/about](https://murage.ai/about) | | Releases | [Every installer](https://github.com/FerroxLabs/murage-releases/releases) · [What changed](https://murage.ai/changelog) | | Security | [How we handle data, and how to report a problem](SECURITY.md) | | Contributing | [How to contribute](CONTRIBUTING.md) | ## Credits and license Murage is developed and maintained by **Ferrox Labs**. It started from [OpenMausBot](https://github.com/milind-soni/OpenMausBot), created by Milind Soni and its contributors. Murage is independently maintained and is not affiliated with or endorsed by the upstream project. Licensed under the GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later). See [LICENSE](LICENSE) and [NOTICE](NOTICE). Murage builds on OpenMausBot; those portions remain under the Apache License 2.0 ([LICENSES/Apache-2.0.txt](LICENSES/Apache-2.0.txt)). Bundled third-party components retain their own licenses and attribution. Murage is a trademark of Ferrox Labs, LLC (US application serial 50181085). The Murage and Ferrox Labs names and logos are not covered by the code license; see [TRADEMARKS.md](TRADEMARKS.md).

Cargando el README del repositorio…

Skills en este repositorio

Desarrolladores de software Analistas de garantía de calidad de software y probadores

2 categorías ocupacionales · 0% clasificado

sin clasificar

Generates activity ideas organized by age band (0-2, 2-5, 5-8, 8-12, 12+) with developmental rationale for each activity. Produces categorized activity lists with materials needed, time estimates, and the specific developmental skills each activity supports.…

Idioma del texto original: inglés

2026-10-07

Mostrando 40 de 2253 skills recopiladas.