hum
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 9 GitHub stars
Code Basarisiz
- process.env — Environment variable access in drone/llm.ts
- network request — Outbound network request in drone/llm.ts
- process.env — Environment variable access in fs/config.ts
- exec() — Shell command execution in fs/linguistic.ts
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
your sanctuary for multiplexed cross-harness AI bots
\_ hum _/
A sentinel for your multiplexed cross-harness AI bots.
Supported today: + OpenCode session governance + Claude Code providers in headless (compliant) mode
curl -fsSL https://raw.githubusercontent.com/adiled/hum/main/install | bash
hum (/klwʊnd/).
hum update
hum status
hum logs
hum sessions
hum uninstall
Needs git, node (v20+), pnpm, opencode, claude.
Core workflow is operational (more coming). See compatibility.
Config ~/.config/hum/hum.json
| Key | Default | Description |
|---|---|---|
maxProcs |
4 |
Max concurrent Claude CLI processes |
idleTimeout |
30000 |
Kill idle process after ms (0 = disabled) |
smallModel |
"" |
Override small model (empty = auto-discover free model) |
permissionDusk |
60000 |
Permission prompt timeout in ms before auto-deny |
droned |
false |
Enable the drone — stream observer, context-loss detection, auto-recovery |
droneModel |
opencode-hum/claude-haiku-4-5 |
Model for drone LLM assessments |
External MCP
MCP servers configured in opencode.json are available to Claude. hum's daemon spawns and proxies local MCP servers (e.g. context7). Auth-bound (OAuth) MCPs are not yet supported.
hum denies file writes in directories parent to cwd. Until ask is supported for that, you can use opencode-dir plugin's /cd and /mv commands to relocate your session to the desired directory.
Tips
hum currently relies on opencode as the harness because of thorough customizability. Utilize its configuration to the fullest.
- hum sanitizes prompts to ensure undisrupted usage, ensure any custom prompts do not depend on xml tags and second-person attributions
- hum greatly strips away commonly expected file system tools by any harness, with more superior code and non-code tooling, but does not dictate prompt engineering or reminders around them yet, so take control of that as needed
- hum code analysis and authoring tools
readdo_codeare pure AST-based and are limited to few languages, non-code writing tooldo_nocodecan be relied on for yet unsupported languages
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi