Skip to content

rse/ase / plugin/skills/ase-meta-config

ase-meta-config

Verified

List, get, set, or delete the layered ASE configuration values across the user/project/task/session scope chain. Use when the user wants to "configure" ASE, or to inspect or change a configuration key like `agent.persona`, `agent.guidance`, `project.boxing`, or `project.task.lifecycle`.

FileKindSize
SKILL.mdskill md6.8 KB
help.mdmarkdown7.9 KB

##  NAME

`ase-meta-config` - Configuration Management

##  SYNOPSIS

`ase-meta-config`
    [`--help`|`-h`]
    [`--scope`|`-s` *scope*]
    *operation*
    [*args*]

##  DESCRIPTION

The `ase-meta-config` skill lists, reads, writes, and removes the values
of the *layered ASE configuration* from inside the assistant session. It
mirrors the non-interactive subcommands of the `ase config` CLI, but
performs *every* access through the `ase_config_list`, `ase_config_get`,
`ase_config_set`, and `ase_config_delete` tools of the `ase` MCP server -
it never shells out and never touches a file directly.

The configuration is organized as a chain of *scopes*, canonically
ordered `default` < `user` < `project` < `task` < `session`. Reads
cascade from the strongest (rightmost) scope down to the weakest and
return the first value that is defined; writes are always confined to
the strongest (target) scope of the chain. With `ASE_CONFIG_DIR` set,
the read-only `override` scope of `$ASE_CONFIG_DIR/override.yaml` is
read directly below `session`, overriding even `project` and `task`.

The recognized keys are grouped under `project.*` (`project.id`, `project.name`,
`project.boxing`, `project.users`, `project.task.lifecycle`, `project.task.idscheme`,
`project.task.store.{url,token,crt,key}`, `project.task.default.{source,changeset,target}`,
`project.task.effort.{scale,factor,file,line,iteration}`, `project.relay.{url,token,crt,key}`,
`project.service.port`, the `project.artifact.`*kind*`.{basedir,files}` globs, and
`project.artifact.spec.schema`), `agent.*` (`agent.persona`, `agent.guidance`,
`agent.diagram.{format,theme,tone}`, and `agent.cache.{guard,threshold,soft,hard}`),
`telemetry.*` (`telemetry.{enabled,implicit}`, `telemetry.service.{port,token,interval,idle}`,
and `telemetry.prices.{ai,hr}`), and `board.*` (`board.{tui,web}.color.{dim,normal,accent,signal}`,
`board.web.editor.keymap`, and `board.web.theme`); see `ase man config` for details.

Some keys are writable on selected scopes only; in particular all
`project.*` keys except `project.id`, `project.name`, and `project.boxing`,
as well as all `telemetry.*` and `board.*` keys, are writable on the
`user` and/or `project` scopes only. The values of the secret keys
`project.task.store.token`, `project.relay.token`, and
`telemetry.service.token` are reported masked as `***`. The internal
session state, like the active task id (see `ase-task-id`), is not part
of the configuration.

The four keys steering the behaviour of the agent itself accept fixed
value sets: `agent.persona` selects the *communication style* and is one
of the decorative, eloquent, and explaining `writer`, the concise,
factual, and accurate `engineer` (the default), the layered,
pyramid-structured `journalist`, the brief, factual, and abbreviating
`telegrapher`, or the terse, rough, and stuttering `caveman`;
`agent.guidance` selects the number of unsolicited hints and is one of
`none`, `minimal`, `normal` (the default), or `verbose`;
`agent.diagram.format` selects the rendering of the diagrams of the skills and is
one of `auto` (the default, an inline image if the terminal probe at session
start detects support for it, else text), `image` (always an inline image), or
`text` (always text); and
`project.boxing` selects the artifact transparency and is one of `white`,
`grey`, or `black`. Setting `agent.persona`, `agent.guidance`,
`agent.diagram.format`, or `project.boxing` takes effect immediately, i.e. still
within the running session. Additionally, `project.task.lifecycle` selects the task plan
lifecycle and is one of `solo` (the default), `team`, or `enterprise`; it is
exported at session start as `<ase-project-task-lifecycle/>`. Finally,
`project.task.idscheme` selects the scheme of newly generated task ids and is one
of `slug[:<words>]` (the default, the first *words* (default: 2) words of
the task title, lower-cased and joined with `-`), `seq[:<template>]` (a
continuously increasing sequence number, rendered through a sprintf-style
*template* like `FOO-%03d`, `#%d`, or `%d` (the default)), or `any` (an
arbitrary unique id chosen by the agent). Additionally,
`project.task.default.{source,changeset,target}` select the defaults of
the `Source:`, `Changeset:`, and `Target:` task plan keys (`worktree`,
`worktree`, and `source` by default), which an absent key reads as, where
a `branch:<name>` or `attachment:<name>` value can carry the placeholder
`{id}` of the task id (e.g., `branch:cs-{id}` for a branch per task); they
are exported at session start as
`<ase-project-task-default-{source,changeset,target}/>`.

The diagram images are styled by `agent.diagram.theme`, one of `auto`
(the default, probing the terminal background for one of the others),
`light` (dark node boxes with light labels), or `dark` (vice versa), and
`agent.diagram.tone`, one or two theme colors `#rgb` or `#rrggbb`
(default: `#336699`), where a missing second color is derived as the
complement of the first one (a brown for the default blue).

The following *operations* exist:

- `list`: List all effective configuration entries of the scope chain as
  a table of key, value, and the scope that supplied the value. For
  overlapping keys only the value of the strongest scope is shown.

- `get` *key*: Report the effective value at the dotted *key*, or
  `(not set)` if no scope of the chain defines it.

- `set` *key* *value*: Write *value* at the dotted *key* on the target
  scope. The value is validated against the configuration schema before
  it is persisted.

- `delete` *key*: Remove the value at the dotted *key* from the target
  scope. A key that is not present is silently ignored.

The `init` and `edit` subcommands of the `ase config` CLI are
deliberately *not* mirrored: `edit` is bound to an interactive terminal UI
and therefore has no meaning inside an assistant turn, and `init` is a
preset-bootstrapping operation that stays a shell concern next to
`ase setup`. Both remain available as `ase config init` and
`ase config edit` on the command line.

##  OPTIONS

-   `--scope`|`-s` *scope*:
    The scope chain to operate on, given as a comma-separated list of
    `user`, `project`, `task:`*id*, and/or `session:`*id* terms, in any
    order and at most one term per kind. The `user` term is always
    implicitly added at the bottom of the chain, and `project` is
    implicitly added whenever a project context exists, but never above
    the strongest explicitly requested term. If the option is
    omitted, the chain of the *current session* (`session:`*id*) is used,
    so that reads see the full `user` -> `project` -> `session` cascade
    and writes land on the session layer.

##  ARGUMENTS

-   *operation*:
    The operation to perform; one of `list`, `get`, `set`, or `delete`.

-   *args*:
    The operands of the operation: none for `list`, a dotted *key* for
    `get` and `delete`, and a dotted *key* plus a *value* for `set`.

##  SCENARIOS

-   You want the ASE configuration inspected or changed
-   You want the persona, guidance, diagram format, or boxing switched for a session
-   You want a configuration value persisted at user or project scope
-   You want to see which scope supplies each effective value

##  EXAMPLES

List all effective configuration entries:

```text
❯ /ase-meta-config list
```

Report the effective persona style:

```text
❯ /ase-meta-config get agent.persona
```

Switch the communication style for the current session only:

```text
❯ /ase-meta-config set agent.persona telegrapher
```

Switch the project boxing for the current session only:

```text
❯ /ase-meta-config set project.boxing grey
```

Persist the guidance level for the whole project instead:

```text
❯ /ase-meta-config --scope project set agent.guidance minimal
```

Persist the task lifecycle for the whole project:

```text
❯ /ase-meta-config --scope project set project.task.lifecycle team
```

Remove a value from the user-level configuration:

```text
❯ /ase-meta-config --scope user delete project.name
```

##  SEE ALSO

[`ase-task-id`](../ase-task-id/help.md).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall