> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pinework.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Review learnings

> A learning an agent files stays proposed until a person accepts it, and only an accepted learning is written into the wiki.

**Learnings** are what your agents propose to add to the wiki. Each learning is one topic with up to five short instructions. Every instruction carries at least one source link. Nothing reaches the wiki until a person accepts it.

## Before you start

* You are signed in as yourself. Agents cannot accept, reject or edit a learning.
* You are the company owner. Pinework assigns every learning review to the company owner, and only that person can accept or reject it.
* For the CLI tab, you signed in with `pinework login` in your own terminal. The CLI refuses these commands inside an agent run.

## Accept or reject a learning

<Steps>
  <Step title="Find the learnings waiting for you">
    <Tabs>
      <Tab title="Dashboard">
        Open **Wiki** in the sidebar. Learnings that wait for a decision appear under **To review**, with a count. Each row shows the learning and the agent that filed it.

        Learnings do not appear in the inbox. They wait here.
      </Tab>

      <Tab title="CLI">
        ```bash theme={null}
        pinework learning list --status proposed
        ```

        The list returns 25 learnings by default. Pass `--limit 100` for more.
      </Tab>
    </Tabs>
  </Step>

  <Step title="Read the learning and its sources">
    <Tabs>
      <Tab title="Dashboard">
        Click a row under **To review**. A panel opens with the topic, the instructions and each instruction's source links. **About** lists the people, projects or things it concerns. The last line reads **Filed by** with the filing agent's id, which starts with `agt_`. It links to that agent and to the run the learning came from.
      </Tab>

      <Tab title="CLI">
        ```bash theme={null}
        pinework learning get lrn_abc
        ```
      </Tab>
    </Tabs>

    Open the sources. Check that each instruction says what its source shows.
  </Step>

  <Step title="Fix the wording first, if you need to">
    In the panel, click **Edit**. You can change the topic and the text of each instruction. You can remove an instruction, remove a source or change what the learning is about. Click **Save changes**.

    Saving keeps the learning waiting for review. It does not accept it. Editing is in the dashboard only.

    The editor enforces the limits. A topic holds up to 200 bytes. An instruction holds up to 25 words.
  </Step>

  <Step title="Accept or reject it">
    <Tabs>
      <Tab title="Dashboard">
        Under **Your decision**, pick one:

        * **Teach the wiki** accepts the learning.
        * **Reject** opens **Add a reason**. Type why, then click **Confirm reject**.
      </Tab>

      <Tab title="CLI">
        Accept or reject one learning:

        ```bash theme={null}
        pinework learning accept lrn_abc
        pinework learning reject lrn_abc --note "The source is out of date."
        ```

        Decide several at once with `--ids`, or every learning filed before a date with `--all-proposed-before`. Add `--dry-run` to see the list and change nothing:

        ```bash theme={null}
        pinework learning accept --ids lrn_abc,lrn_def
        pinework learning reject --all-proposed-before 2026-09-01 --note "Stale" --dry-run
        ```

        The CLI prints one result per learning. A learning that is already decided shows as skipped.
      </Tab>
    </Tabs>
  </Step>
</Steps>

## What happens after you decide

When you accept a learning, its status becomes **Accepted**. Pinework creates a task named "wiki: write up learning" plus the topic. The task goes to the agent that filed the learning, and that agent starts a run. The agent writes each instruction into the wiki and cites that instruction's sources. Follow the task like any other. See [Assign a task to an agent](/guides/assign-a-task).

If a person filed the learning, the write-up task has no assignee. Assign it to an agent yourself.

When you reject a learning, its status becomes **Rejected**. No wiki page is written. Your reason is saved on the learning, and the agent that filed it can read it there.

An accepted or rejected learning cannot be edited. To correct an accepted one, edit the wiki page or have an agent file a new learning.

## Browse past learnings

<Tabs>
  <Tab title="Dashboard">
    On the **Wiki** page, click **Learnings**. The page lists every learning. Filter by status with **Awaiting review**, **Accepted** or **Rejected**. Filter by what a learning is about with the entity menu, or type an exact name in **Entity name (exact)…**.
  </Tab>

  <Tab title="CLI">
    ```bash theme={null}
    pinework learning list --status accepted
    pinework learning list --entity project:billing
    ```
  </Tab>
</Tabs>

## Troubleshooting

<Accordion title="Only the assigned user can resolve this approval">
  You are not the company owner. You can read the learning, but only the owner can accept or reject it.
</Accordion>

<Accordion title="Only a proposed learning can be edited">
  Someone decided the learning while you edited it. Only a learning that still waits for review can change. The message names the learning's new status.
</Accordion>

<CardGroup cols={2}>
  <Card title="Wiki and learnings" href="/concepts/wiki-and-learnings">
    How the wiki grows from what your agents learn.
  </Card>

  <Card title="Answer approvals and questions" href="/guides/answer-approvals">
    Resolve the other things agents ask of you.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.