HoneClaw: a Rust investment research assistant that argues with your trades

What HoneClaw is for, and who it is aimed at

Most assistants built around language models are tuned to agree. HoneClaw's README states the opposite intent in its opening lines: it describes the project as "not a chat toy designed to indulge you, but a ruthless defender of your investment discipline." The name comes from the same idea. To hone is to sharpen an edge, and the README frames serious investing as research, comparison, review and long-term discipline rather than reacting to every headline.

The audience is a single investor who already keeps positions and wants a co-pilot that checks decisions against data and predefined rules. The README lists the jobs it takes on: tracking developments at companies you hold, enforcing investment discipline, running scheduled monitoring tasks, and countering emotional trading impulses. That is a narrower scope than a general chatbot and a much narrower scope than a brokerage platform. HoneClaw does not place orders. It argues with you, monitors conditions you define, and writes down what it learns.

How the Rust workspace is put together

The repository is a Cargo workspace, and the member list is the clearest map of the architecture. crates/hone-core, crates/hone-llm, crates/hone-tools, crates/hone-integrations, crates/hone-scheduler, crates/hone-channels and crates/hone-event-engine carry the shared logic. Each delivery surface is its own binary: bins/hone-cli, bins/hone-web-api, bins/hone-imessage, bins/hone-feishu, bins/hone-discord, bins/hone-telegram, bins/hone-desktop, bins/hone-user-app and bins/hone-mcp. There are also three agent adapters (agents/function_calling, agents/gemini_cli, agents/codex_cli) and a memory crate, which matches the README's claim that company profiles and event timelines accumulate as Markdown.

The stack is Rust end to end for the core, with Tokio, Axum and SSE on the server side, Tauri for the desktop client, and SolidJS with Tailwind on the front end. The workspace version is 0.15.3 and the edition is 2024, so a stable toolchain that supports Edition 2024 is a hard requirement rather than a preference. The JavaScript side is a separate Bun workspace: package.json sets packageManager to [email protected] and exposes scripts such as build:web, dev:desktop and build:desktop. If you only want the Rust service, the Bun layer is not on your path.

Installing HoneClaw and running a first session

The README gives three installation routes. The one-line installer is the shortest. It fetches a shell script from the repository and pipes it to bash, then you run three CLI commands in sequence. The doctor command checks the environment, onboard walks you through initial setup, and start launches the service.

curl -fsSL https://raw.githubusercontent.com/B-M-Capital-Research/honeclaw/main/scripts/install_hone_cli.sh | bash
hone-cli doctor
hone-cli onboard
hone-cli start

On macOS or Linux you can install through Homebrew instead, using the tap path the README gives. The three CLI commands after it are identical, so the choice only affects how the binary arrives on disk.

brew install B-M-Capital-Research/honeclaw/honeclaw
hone-cli doctor
hone-cli onboard
hone-cli start

The Web interfaces are started separately, in another terminal. The README names two: an admin UI and a user UI.

hone-cli web admin-ui
hone-cli web user-ui

For development, clone the repository and run the CLI from source with the build flag, then start each Web surface with its own dev flag in separate terminals.

git clone https://github.com/B-M-Capital-Research/honeclaw.git
cd honeclaw
cargo run -p hone-cli -- start --build
cargo run -p hone-cli -- web admin-ui --dev
cargo run -p hone-cli -- web user-ui --dev

The README points to docs/wiki.md for the full startup matrix, directory guide, ports, configuration and troubleshooting, and to config.example.yaml for configuration. It does not list the port numbers in the README itself, so read the wiki before you expose anything. A docker-compose.dev.yml and a .env.example sit at the top level; the example file shows a local PostgreSQL on port 5433 with user honeclaw and database honeclaw, which is the development credential set, not a production one.

The parts the public repository does not contain

The maintainer's note is unusually direct: "a number of professional valuation tools, investment research workflows, and proprietary knowledge bases are not included in this public repository." That sentence should shape how you read everything else. The open code gives you the assistant shell, the channels, the scheduler, the memory format and the Web interfaces. It does not give you the valuation models the product is sold on. If your reason for cloning is to inspect how HoneClaw values a company, the repository will not answer that question.

The .env.example reinforces the split. It carries Stripe configuration for a hosted offering: HONE_STRIPE_MODE, HONE_STRIPE_SECRET_KEY, HONE_STRIPE_WEBHOOK_SECRET, HONE_STRIPE_PRODUCT_ID, a recurring yearly price variable and a one-time price variable, with HONE_STRIPE_CHECKOUT_ENABLED set to false by default. There are also advertising flags for Alipay and WeChat Pay that the file says change copy only and fail closed. In other words, the repository is the client side of a commercial product, and the environment file assumes that framing. Anyone expecting a complete self-contained research stack should treat that as the primary limitation, not a footnote.

Where HoneClaw is the wrong tool

HoneClaw assumes a Unix-like environment. The README recommends macOS or Ubuntu and does not describe a Windows path, so a Windows workstation means WSL or a different tool. It also assumes you can run a Rust build with Edition 2024 support and, for the Web surfaces, a Bun 1.3.9 workspace. That is a developer's machine, not a locked-down corporate laptop.

The second limit is scope. HoneClaw monitors positions, alerts on conditions, and runs scheduled briefings. It is not an execution system, and the README never claims order routing or broker connectivity. If you need fills, reconciliation and tax lots, this is the wrong layer. The third limit is memory. Company portraits are stored as Markdown, which is portable and readable, but it also means the quality of the research asset depends on what gets written into those files. A scheduled job that writes noise produces a noisy knowledge base.

Finally, the licensing note deserves reading before you plan a fork. The repository is MIT, but the maintainer's note says the professional valuation tools and proprietary knowledge bases are not in it. MIT covers the code you can see. It does not grant you the missing pieces, and the README does not explain how, or whether, they can be obtained beyond inviting interested readers to get in touch.

How HoneClaw differs from a general assistant stack

The obvious alternative is a general-purpose agent framework wired to an LLM API and a cron runner. The difference is in what ships in the box. A generic stack gives you a model loop and leaves channel adapters, scheduling, persistence and a UI to you. HoneClaw ships all four as workspace members: hone-channels, hone-scheduler, hone-event-engine and hone-web-api, plus ready binaries for Feishu, Discord, Telegram, iMessage and a Tauri desktop app. You trade flexibility for a fixed opinion about how an investment assistant should be shaped.

A second comparison is a hosted research terminal. Those give you the data and the valuation models but keep your notes inside their system. HoneClaw inverts that: your company portraits live as Markdown files in a directory you control, and the missing valuation layer is the thing you would buy. Which one is right depends on whether you value owning the memory or owning the models. HoneClaw's bet is that the memory is the durable asset, and the README's framing of company portraits as "a reusable long-term research asset" is consistent with that bet.

Maintenance, releases and what the licence does not cover

The workspace version is 0.15.3, and the release history shows a tight cluster: v0.15.1, v0.15.2 and v0.15.3 all landed within roughly a day of each other, the last one on 2026-07-27. The repository has not been pushed since that date and is not archived. A reader deciding today should treat the project as one whose last recorded activity was on 2026-07-27 rather than as something with a steady cadence, and should check the release page themselves before depending on a fix.

The upgrade cost is dominated by the toolchain. Edition 2024 in Cargo.toml means an older Rust toolchain will not build the workspace, and the Bun workspace pins [email protected] through packageManager, so a mismatched Bun will behave differently from the documented one. Configuration lives in config.example.yaml and the environment file, and the .env.example comments say Stripe secrets are deployment-specific: the local stripe listen secret, a registered test endpoint and a registered live endpoint each have a different signing secret. Copying one into another environment is the failure mode the file warns about.

The licence is MIT, which is permissive and short. It covers the source in this repository. It does not cover the valuation tools, research workflows or proprietary knowledge bases that the maintainer's note says are excluded, and the README describes no separate licence for those. Treat the MIT grant as applying to the code you can clone and nothing beyond it. This is a description of what the files say, not legal advice.

Editorial conclusion

Adopt HoneClaw if you want a self-hosted research assistant that stores company notes as Markdown files and reaches you through Feishu, Discord, Telegram or iMessage, and if you are comfortable building a Rust workspace with Edition 2024. Do not adopt it if you expect the repository to contain the valuation models and proprietary knowledge bases: the maintainer's note says those are not included, so the public code is the shell around a paid product. Before committing, run hone-cli doctor and hone-cli onboard on your target machine, open docs/wiki.md for the port and configuration matrix, and read .env.example to confirm which Stripe variables your deployment will actually need. The repository was last pushed on 2026-07-27 and is not archived.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes