cosmo answer

CLI · 09

Be the human in the loop from the shell. cosmo answer watches a namespace for CLARIFICATION / PERMISSION requests and prompts you for each one. By default it emits the discrete CLARIFICATION_ANSWER / PERMISSION_DECISION signal (consumed via await_decision() or the matching handlers); pass --redispatch to instead close the loop by re-dispatching a follow-up TASK to the asking Neuron.

$ cosmo answer --help

Interactively answer CLARIFICATION / PERMISSION requests.

Usage
  cosmo answer --url <url> [options]

Options
  --url <url>             Synapse URL (cosmo:// | nats:// | kafka://). Required.
  --namespace, -n <ns>    Namespace to watch.                 Default: dev
  --trace <trc_…>         Only answer requests on this trace.
  --redispatch             Reply by re-dispatching a follow-up TASK to the asking
                           Neuron (respond_to_clarification / respond_to_permission)
                           instead of emitting a discrete answer signal.

Example

$ cosmo answer --url=cosmo://127.0.0.1:7070 -n dev
  watching namespace 'dev' for CLARIFICATION / PERMISSION (Ctrl-C to quit)

  [trc_01JV…] CLARIFICATION from neuron=answerer
    question: Which topic?
  your answer: billing
  → CLARIFICATION_ANSWER emitted (parent_id = the request's id)

Have a feature in mind?

The protocol, SDKs, and CLI are still pre-1.0. If something here is missing, ambiguous, or wrong - open an issue and propose a change. Every breaking change is debated in DECISIONS.md first.

Run the quickstart →Re-read the envelope spec