Yapitalism

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/aytuncyildizli-yapitalism

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 26, 2026.

Tools

4 read · 4 write · 1 delete · 4 not yet classified

Secrets

None asked for

Install scripts

Runs code on install

Runs as

Python package

Tools (13)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• hermes_list

  List the Hermes gateways this machine's user has registered. Read-only. Peers come from `hermes peer add` — Hermes owns the registry and the credentials; nothing is configured or stored on this side, and nothing is hardcoded. An empty list is an answer: register a gateway with `hermes peer add <name> --url http://host:port --key <API_SERVER_KEY>`. A multiplexed peer hosts named agent profiles addressed as `<peer>/<agent>` in the task tools; Hermes does not enumerate a peer's profiles remotely, so ask the peer's operator what exists.

• hermes_task_send

  Submit one task to a Hermes agent and return ACCEPTED with a run id. This is a WRITE to another agent. Name the target and the task in one sentence and get an explicit confirmation before calling it. `target` is `<peer>` or `<peer>/<agent>` as registered with `hermes peer add`. The task runs as its OWN asynchronous turn on the peer (Hermes `peer run`), never inside an existing chat — an ongoing WhatsApp conversation cannot be interrupted by this tool. `state` is the only thing to speak from, and `accepted` is its ceiling here: a run id proves the peer took the task, not that anything was do…

• hermes_task_status

  Read one Hermes task's progress by run id. Read-only. `state` is accepted / working / completed / blocked / unknown, derived only from Hermes's own status word — never from an HTTP round-trip succeeding. `completed` additionally requires final output to exist; `unknown` carries Hermes's raw answer so nothing is guessed. Never speak `completed` from any other state.

• pane_await

  Wait until the agent's TURN in a pane ends, and say how it ended. Read-only: this never types. It watches the pane and returns one of: - `ended` the prompt is idle and the screen stopped changing. This means the TURN is over — it is NEVER proof the work is correct, and must not be spoken as "done". - `waiting_input` a blocking dialog is on screen (trust / login / confirmation). The operator is the blocker; tell them. - `agent_error` a known failure line owns the screen (401, "please run /log…

• pane_clear

  Try to unstick a pane whose prompt is blocking a send. For when `pane_send` came back RED with `rejected_prompt_not_empty` (text is already sitting in the box) or `rejected_prompt_unreadable` (a menu or overlay is covering it). `action` is one of a fixed set — there is no way to send an arbitrary key: - `escape` dismiss a dialog or cancel the current input - `clear-line` empty an input that already holds text - `escape-twice` for TUIs that need to leave an inner mode first Enter is not in that set and never will be. Escape cancels, Enter commits: on a menu, Enter picks what…

• pane_read

  Read recent visible output from one pane. `target_id` comes from panes_list and must stay namespaced, e.g. `tmux:%0`. Read-only: this never types into the pane. Output is the pane as rendered, so it may hold wrapped lines, prompts and ANSI leftovers — summarize it rather than reading it aloud verbatim.

• pane_send

  Send text to a pane and return a receipt for what was actually proven. This is a WRITE. Name the target and the action in one sentence and get an explicit confirmation before calling it. `status` is the only thing to speak from: - GREEN the agent demonstrably processed the text. - YELLOW the write landed but processing was NOT proven. Say so. Never round a YELLOW up to "done" — text sitting unread in a prompt box looks identical to work in progress from the outside. - RED the backend refused the write; nothing reached the terminal. `missing_guarantees`, when present, lists…

• pane_task

  Send text, then wait until the agent's turn ends. Two receipts in one. This is a WRITE (the send half follows every `pane_send` rule, including the explicit-confirmation requirement). After a dispatched send it watches the pane and reports how the turn ended: `ended`, `waiting_input` (with the blocking question), `agent_error` (named), `exited`, `running`, or `unreadable` — see `pane_await` for what each claims and does not claim. The `send` and `turn` receipts come back separately and `speak` composes them. An `ended` turn is not "task complete": it says the agent stopped, nothing more. If …

• panes_create

  Start a new agent in a fresh tmux session and report what actually runs. This STARTS A PROCESS. Name the runtime and the working directory in one sentence and get an explicit confirmation before calling it. `runtime` must be one of codex, claude, kimi. It selects a fixed launcher — there is no way to pass a command, arguments, or flags through this tool, and asking for one is a request to run arbitrary code by voice. `cwd` must already exist; it is the directory the agent will work in. Say it back to the operator before calling, because an agent started in the wrong repo will happily edit t…

• panes_list

  List agent terminal panes on this machine, across every backend. Each pane carries: - `target_id`, namespaced (`tmux:%0`). Use it verbatim for any later call. - `runtime`: codex, claude, kimi, opencode, shell, or unknown. Anything that is not an agent runtime is NOT addressable — a pane that used to run an agent and now runs a plain shell would turn an instruction into a shell command. - `missing_guarantees`, when present: protections that backend cannot enforce. Never describe such a pane as being as safe as one without it. Naming a pane out loud: match on `project`, `…

• panes_name

  Bind a spoken name to a pane, so later calls can say `billing` for `tmux:%4`. The binding records what the pane RUNS right now (runtime, folder), and every later use re-verifies it against a live listing: a name whose pane disappeared or changed runtime is refused, never silently retargeted. This changes where future writes route, so it passes the same write authority gate a send does. Names are lowercase words (letters, digits, hyphens, max 32); they may not shadow a backend or peer namespace.

• panes_resume

  Bring a dead agent back in a fresh tmux session, and say how faithfully. This is a WRITE that starts a process. Name the runtime and the directory in one sentence and get an explicit confirmation before calling it. `runtime` is one of codex, claude, kimi and selects a fixed resume form — as with `panes_create` there is no way to pass a command or flags, because asking for one is a request to run arbitrary code by voice. `session_id` is optional and it changes what can honestly be claimed: - given `fidelity: "exact"` — that recorded session was asked for. - omitted `fidelity: "last"…

• panes_unname

  Forget a spoken name. The pane itself is untouched.

Signals

Stars

7

Forks

1

Open issues

0

Weekly downloads

26

Last commit

Oct 15, 2026 (13 days ago)

Last release

Aug 24, 2026 (2 months ago)

Last package publish

Aug 24, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name

io.github.AytuncYildizli/yapitalism

Version

0.6.0

Auth

No auth

Packages

pypi yapitalism

License

MIT

Repository

github.com/AytuncYildizli/yapitalism

Website

yapitalism.com

First seen

Oct 24, 2026

Last checked

Oct 25, 2026

Source

Official MCP Registrygithub-graphql