agentlas-connect
FreeConnect Agentlas agents or teams to Telegram.
The English summary is being prepared. Showing the original description.
Connect Agentlas agents or teams to Telegram.
The English summary is being prepared. Showing the original description.
Build, repair, or package Agentlas agents and teams with Hephaestus.
The English summary is being prepared. Showing the original description.
Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion.
The English summary is being prepared. Showing the original description.
Use when the user types /hep-graph or asks to create, list, inspect, or request a run of an Agentlas automation graph.
The English summary is being prepared. Showing the original description.
Use when generating a single installable agent that should keep learning, track sources, refresh research, propose repairs, or improve itself over time without becoming a multi-agent team.
The English summary is being prepared. Showing the original description.
Use when the user types /agentlas-upload, /agentlas upload, $hephaestus-upload, or /hep-upload to scan, gate, and publish an agent/team package to Agentlas Cloud (private) or Agentlas Hub (public).
The English summary is being prepared. Showing the original description.
Prepare explicitly named Agentlas Hub or Cloud agents.
The English summary is being prepared. Showing the original description.
Use when adding or auditing local runtime behavior that turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files.
The English summary is being prepared. Showing the original description.
Use when the user types /agentlas-local, /agentlas local, or /hep-local to staff only from registered Local packages.
The English summary is being prepared. Showing the original description.
Use when designing a new multi-agent team, visible agents folder, role boundaries, handoff flow, PM Soul, Memory Curator, Policy Gate, or evaluation role. Use for agent-team repo creation even when the user only says they want a meta-agent or agent operating system.
The English summary is being prepared. Showing the original description.
Use when the user types /agentlas-call <agents> <context>, /agentlas call, or /hep-call to borrow and execute named Agentlas Hub/Cloud agents attached to the current project.
The English summary is being prepared. Showing the original description.
Use when the user types /agentlas-graph, /agentlas graph, or /hep-graph to create, list, inspect, or run Agentlas automation graphs.
The English summary is being prepared. Showing the original description.
Single entry point for every Agentlas command: /agentlas network, /agentlas build, /agentlas storm, /agentlas graph, /agentlas one, /agentlas upload, /agentlas cloud, /agentlas hub, /agentlas local, /agentlas browser, /agentlas call, /agentlas search, /agentlas connect, /agentlas login, /agentlas orch, /agentlas update.
The English summary is being prepared. Showing the original description.
Use when the user types /hep-cloud or /agentlas-cloud, or asks to staff from THEIR OWN Agentlas cloud packages only. Cloud is one exact source scope; Network means Local + owner Cloud + public Hub.
The English summary is being prepared. Showing the original description.
Use when the user types /hep-storm or /agentlas-storm, says @Hephaestus storm <goal>, or asks to drive a goal to verified completion through a force-robust Stormbreaker loop. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs each work packet as a verifier-first hardened loop that does not stall, run away, or claim false success. Use it for loop-worthy work — apps, sites, agents, automations, debugging, multi-step research, data/report generation. Trivial questions are answered directly, not stormed.
The English summary is being prepared. Showing the original description.
Use when the user types $hephaestus-upload, /hep-upload, or /agentlas-upload, or asks to upload, publish, or list an Agentlas agent or team. Ask Cloud (private) vs Agentlas Hub (public) FIRST, then publish through the bundled Hephaestus gate.
The English summary is being prepared. Showing the original description.
Use before claiming that the package can be installed or published. Verifies structure, adapters, schemas, executable scripts, and public-safety boundaries.
The English summary is being prepared. Showing the original description.
Use when designing how one canonical agent core runs across Codex, Claude Code, Antigravity, Cursor, and AGENTS.md-compatible tools.
The English summary is being prepared. Showing the original description.
Use when adding Memory Events, Memory Tickets, memory-map.json, vault-references.json, PM Soul memory ownership, or Memory Curator routing to an agent repo.
The English summary is being prepared. Showing the original description.
Use when preserving product intent, acceptance criteria, decision memory, open loops, roadmap context, or the product-manager continuity layer of an agent team.
The English summary is being prepared. Showing the original description.
Use when packaging this meta-agent for public Codex plugin registration, Claude Code installation, GitHub release, one-line terminal install, or open-source distribution.
The English summary is being prepared. Showing the original description.
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.
The English summary is being prepared. Showing the original description.
Use when creating Codex, Claude Code, Antigravity, Cursor, or AGENTS.md runtime adapters from one canonical agent core. Use whenever a generated repo needs multiple AI runtimes without duplicating instructions.
The English summary is being prepared. Showing the original description.
Use when creating or auditing an agent-team sitemap, Task Bias ledger, concept coverage, product surface map, validation chain, or missing-concept check.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)