On Knowledge, Upload adds a file to the current area (or Unfiled). Hub Upload accepts files up to 25 MB.

A connected agent can upload a file too (up to 8 MB). Larger files stay on this Upload button.

Markdown notes, what we now know, are not files. The agent writes them when work completes, or any time as a note. See Knowledge.

On first project entry, Get Started offers context, a first idea and agent connection. In a populated project, Explore your project’s Knowledge opens your team’s documents. Skip for now allows manual capture without a document. Dismiss hides the checklist; the persistent Get Started control brings it back. The Tour is available on demand (Footer on desktop; the avatar menu on phone).

Connect an agent opens Settings. Completion waits for an actual successful agent request to this project. You can keep planning without an agent or repo.

On Ideas, type in the bar and press Enter. The mic dictates.

The idea lands in the ranked list. Nothing becomes work until you promote it.

Three paths into Ideas:

• Bulk on the Ideas bar, pick a PDF or text file. If the bar already has text, extract from that text instead.
• Knowledge Extract ideas, split a document that is already in Knowledge. Each saved idea keeps a chip back to the source. Review your ideas opens just that saved batch; choose one to develop. Empty results do not count as success, and a partial save retries only unsaved ideas.
• Ask a connected agent to read a local markdown file and capture Ideas. Ceremony and tool names live on Agents.

When an idea is ready, open Develop, row click, grip Enter, or drag the grip onto the Work rail. Those paths only open the drawer. Refine, then Pressure, then Go to Work. Hub classifies Goal, spec, or ticket. You do not pick a destination on the bar.

An empty row does not become work by itself. Go to Work lands on Work as a commitment. The idea stays as a record of where the work came from.

On Work, Ready to start is safe to pick up.

Claim takes ownership. Start begins the ticket. Nothing about the spec's approval or out-of-date work stops a start; Hub shows those problems on the ticket instead.

Same two operations as Agents Claim / Start.

Close with specific evidence, a PR, a commit, a real test run, screenshots. Evidence is optional, but a ticket closed without it shows that on the ticket. A screenshot must be at least 1440×900 and sharp. Hub refuses a smaller or blurry one when it is uploaded. Capture the screen itself at 2x scale, not a thumbnail or a small picture made larger. Finished work shows on Complete.

A human Accept on Complete is extra confidence, not a gate. See Complete.

When something needs a human call, it lands on Work → Needs attention.

Accept, Reject, or Retire covering work…. By default, a Decision an agent logs is already in effect, so it only lands here if work is left on it. A plain proposal, or an in-effect one, can still be accepted, rejected or replaced. See Decisions.

When a ticket completes, the agent that finished it writes what we now know: a new note, or an addition to a document that already covers it. If nothing belongs in Knowledge, it records that and says why. Accept on Complete does not write it.

That write-back is a markdown note, not a file upload. The next loop starts from what you deployed.