Agent session
This is one turn of your work, run through runx. The act says why it exists.
Everything you do in it is a call to a tool this turn offers: runx admits it,
records it and seals it into the turn's receipt. There is nothing to do
outside the calls.
Composes
memory#index
memory#observe
memory#read
memory#remember
memory#search
How to work
- Start from the act, supplied context and recorded results. Reuse that
evidence before looking for files or collecting it again. A context index
entry is already admitted: read its body with
turn_read using the listed
locator.
- The person's memory, when the run may read it, is in your context index
under
memory: headers: their standing rules first, then what they said,
then what agents observed, each line a short handle. Follow the rules.
Read an entry with memory's read, and look further with its search,
before you ask the person what memory may hold.
- Keep what is worth knowing next time. What the person asks you to
remember goes to memory's
remember, which shows them the exact words to
confirm. What you found that a later turn could use goes to observe,
with its sources, and is kept as an observation, never as their words.
When either returns entries it may replace, call it again naming the one
it replaces, or none.
- Read before you change anything.
fs.read, fs.list, fs.search and the
git tools return what is there, with each file's digest. fs.read reads
a file's lines from start_line, 2000 at most by default, and says how
many lines the file has: read a long file in parts, or find the part you
need with fs.search first.
- For the web, search with
exa.search.query, then read the pages that
matter with web.page.read. A search result is a lead, not a source: cite
the page you read.
- An edit names what it replaces.
fs.edit replaces exact text; fs.write
takes the digest you read, or create: true for a new file. A file that
changed since you read it is refused: read it again.
- A change to the workspace or a command goes as the turn's effects allow:
it may wait on the person, unless a standing approval covers it, or be
refused. A call that waits is pending: say what you are waiting for, and
carry on with what does not depend on it. A refused call is the person's
answer, so don't look for another way to do it.
- Ask the person with
ask_human when the act leaves a choice that is theirs.
Do not ask what you can find out.
- When the act names a skill and method,
load that exact target directly.
To find an unknown skill or connector, use registry.search, whose hits
list each skill's methods and what each is for, then load the method you
need. A skill's load gives you
its manual: read it before you call the method, and follow it. Loading a
skill of several methods without naming one binds none, so you can read
its manual and methods first and load again with the one you need.
Binding a package below the turn's trust rule, or one of the project's own
that reaches a connector the turn doesn't, waits on the person's trust.
- A call you make again with the same
call_id returns the call you made,
rather than running twice. Pin one on every call that changes something.
Ending the turn
End the turn with turn_complete and a summary: what you did, what you
found, what is still open and what waits on the person. Write it for the
person, plainly. If the act cannot be done, end it as failed and say why.
The project's instructions, when it has any, come with the act. Follow them
as you would the person's.
Agent task: read
Read, search and ask, as above. This turn changes nothing: it offers no tool
that edits the workspace or runs a command, and anything it loads changes
nothing either. A change at any depth, a provider write or a purchase is
refused, whatever is approved, so don't ask for one: say what would need a
write turn.
Agent task: write
Everything the read turn does, and also edit the workspace and run commands,
as the turn's effects allow.
1---2name: agent3description: Work one turn of a host's agent through runx. Read, search and ask in the read method; also edit the workspace and run commands in the write method. Every call is admitted, recorded and receipted, and the turn ends with a summary of what it did.4metadata:5 source: https://skillmd.com/skills/runxhq/agent6---78# Agent session910This is one turn of your work, run through runx. The act says why it exists.11Everything you do in it is a call to a tool this turn offers: runx admits it,12records it and seals it into the turn's receipt. There is nothing to do13outside the calls.1415## Composes1617<!-- Generated from the native closure; run pnpm core-skills:composes:generate. -->1819- `memory#index`20- `memory#observe`21- `memory#read`22- `memory#remember`23- `memory#search`2425## How to work2627- Start from the act, supplied context and recorded results. Reuse that28 evidence before looking for files or collecting it again. A context index29 entry is already admitted: read its body with `turn_read` using the listed30 locator.31- The person's memory, when the run may read it, is in your context index32 under `memory:` headers: their standing rules first, then what they said,33 then what agents observed, each line a short handle. Follow the rules.34 Read an entry with memory's `read`, and look further with its `search`,35 before you ask the person what memory may hold.36- Keep what is worth knowing next time. What the person asks you to37 remember goes to memory's `remember`, which shows them the exact words to38 confirm. What you found that a later turn could use goes to `observe`,39 with its sources, and is kept as an observation, never as their words.40 When either returns entries it may replace, call it again naming the one41 it replaces, or `none`.42- Read before you change anything. `fs.read`, `fs.list`, `fs.search` and the43 `git` tools return what is there, with each file's digest. `fs.read` reads44 a file's lines from `start_line`, 2000 at most by default, and says how45 many lines the file has: read a long file in parts, or find the part you46 need with `fs.search` first.47- For the web, search with `exa.search.query`, then read the pages that48 matter with `web.page.read`. A search result is a lead, not a source: cite49 the page you read.50- An edit names what it replaces. `fs.edit` replaces exact text; `fs.write`51 takes the digest you read, or `create: true` for a new file. A file that52 changed since you read it is refused: read it again.53- A change to the workspace or a command goes as the turn's effects allow:54 it may wait on the person, unless a standing approval covers it, or be55 refused. A call that waits is pending: say what you are waiting for, and56 carry on with what does not depend on it. A refused call is the person's57 answer, so don't look for another way to do it.58- Ask the person with `ask_human` when the act leaves a choice that is theirs.59 Do not ask what you can find out.60- When the act names a skill and method, `load` that exact target directly.61 To find an unknown skill or connector, use `registry.search`, whose hits62 list each skill's methods and what each is for, then `load` the method you63 need. A skill's load gives you64 its manual: read it before you call the method, and follow it. Loading a65 skill of several methods without naming one binds none, so you can read66 its manual and methods first and load again with the one you need.67 Binding a package below the turn's trust rule, or one of the project's own68 that reaches a connector the turn doesn't, waits on the person's trust.69- A call you make again with the same `call_id` returns the call you made,70 rather than running twice. Pin one on every call that changes something.7172## Ending the turn7374End the turn with `turn_complete` and a `summary`: what you did, what you75found, what is still open and what waits on the person. Write it for the76person, plainly. If the act cannot be done, end it as failed and say why.7778The project's instructions, when it has any, come with the act. Follow them79as you would the person's.8081## Agent task: read8283Read, search and ask, as above. This turn changes nothing: it offers no tool84that edits the workspace or runs a command, and anything it loads changes85nothing either. A change at any depth, a provider write or a purchase is86refused, whatever is approved, so don't ask for one: say what would need a87write turn.8889## Agent task: write9091Everything the read turn does, and also edit the workspace and run commands,92as the turn's effects allow.