Docs
How the Agently office works
One Office. Many Agents. Assign tasks. Build workflows. Stay in control. This guide covers every desk, every switch and the one contract, in the order a task travels.
What the office is
Agently is a virtual agent office on Robinhood Chain. It turns a small team of software agents into something you can see: a pixel office with a front desk, a research lab, a writers' room and a review office. Each agent sits at its own desk, keeps its own queue and may only use the tools you allow. When you hand over a task, you watch it move from room to room, and nothing leaves the office as finished until a person, you, approves it.
The point is control. Agents are fast but they need limits, a record of what they did, and a human at the end. The office gives you all three in one place, without accounts or setup: open the page, pick a look for your visitor, and assign the first task.
The rooms
- Front desk. Pim, the clerk, takes new tasks and keeps the queue. Click the desk in the hallway or the orange "Assign a task" button.
- Research Lab. Nova, the researcher, reads the sources of a task and keeps only what answers the brief.
- Writers' Room. Quill, the writer, turns the research into a draft from a template.
- Review Office. Mara, the reviewer, runs the checklist and hands the task to you for approval.
- Stand-up Room. The task board hangs here. "Call a stand-up" brings everyone in and opens the board.
- Elevator and task notes. The elevator panel holds the tool permissions; the corkboard beside it is the activity timeline.
- Ledger wall. Record an approval on Robinhood Chain, or check a task file someone sent you.
- Break Room and Restroom. Agents with an empty queue rest here between jobs.
Walk with W A S D or the arrow keys, hold Shift to run, click the floor to walk there, click an agent to see what it is doing, and press E next to an agent to talk to it. The mouse wheel zooms and M hides the map.
Assigning a task
A task has a title, a brief and up to six sources. The brief is the question the answer must cover. Sources are the texts the agents may read: paste the text itself, such as meeting notes, an article, a changelog or a support thread. A bare link is not read. Every source gets an id, S1 to S6, that follows it all the way into the draft.
Two switches change the route. Attach live chain readings adds a source S0 with the latest Robinhood Chain block, gas price and the ETH/USD feed, read at the moment the researcher starts. Sensitive stops the task after research and waits for your OK before anything is written, which is the right choice when the material is private or the brief is delicate.
The research desk
The built-in research method is extractive: it never writes a sentence of its own. It splits every source into sentences, scores each one by how many words of the title and brief it shares and how rare those words are across the sources, skips near-repeats, and keeps up to six picks in reading order. Each pick carries its source id. If no sentence shares a word with the brief, the task stops and asks a person to look at the sources or rewrite the brief instead of guessing.
The writers' room
The writer arranges the researcher's picks into one of four templates. It adds structure, never new claims, and every content line ends with its source tag.
- Summary note. A short note: the brief, the key points with sources, open points. Up to 3,000 characters.
- Announcement draft. A headline, a lead and up to four points for a community post. Up to 1,600 characters.
- Status report. Context, findings, which source said what, and gaps. Up to 4,000 characters.
- Post thread. Numbered posts under 270 characters each, one point per post. Up to 3,000 characters.
The review checklist
The reviewer applies the same rules every time and reports each item as pass, warn or fail with the exact line it is about:
- Every claim cites a source: content lines without a [S#] tag, or with an id that does not exist, fail.
- Cited words appear in that source: a line that shares under 60% of its words with the source it cites gets a warning.
- No promises of profit or safety: words such as "guaranteed", "risk-free" or "passive income" fail.
- No personal contact data: email addresses and phone numbers get a warning.
- Length: each template has a ceiling.
- No placeholders left: TODO, TBD and template braces fail.
- Links come from the sources: a link that is in no source gets a warning.
Human approval
A task in the Review column is waiting for you. Open it at the review desk, read the draft and the checklist, and choose: approve it (with an optional note), edit the draft yourself (the checklist runs again on your text), or send it back to the queue with a new brief. A failing item blocks approval until the draft is fixed. Warnings are yours to weigh. Approval is never automatic and no agent can give it.
Tool permissions
The elevator panel lists the tools each agent may be given. New tasks keep a copy of the switches with them, and a step that needs a missing tool stops the task and says which one.
- Clerk: export task files.
- Researcher: read pasted sources, read robinhood chain, use the ai model.
- Writer: use writing templates, read pasted sources, use the ai model.
- Reviewer: run the review checklist, read pasted sources.
Activity timeline
Every hand-off, result, stop, edit and decision lands on the corkboard as one line with the time and the agent, newest first, including errors such as a tool that was not allowed or a model that did not answer. The last 300 lines are kept in your browser and can be exported as JSON.
The optional AI model
The site owner can connect one language model on the server. When it is configured and you switch "Use the AI model" on for the researcher or the writer, that desk sends the task title, brief, template and sources to the model and asks for lines that end with a source id. Lines without a known id are dropped. If the model gives nothing usable, the desk falls back to its built-in method and the timeline says so. The reviewer never uses the model. Calls are rate limited per network, capped per hour for the whole site, and refused for models above a price ceiling.
The ledger contract
AgentlyTaskLedger is a small append-only contract on Robinhood Chain. It has no owner, no admin, no fee, no pause, no upgrade path and accepts no ETH. One call, record(taskHash, resultHash, steps), stores the two keccak-256 fingerprints, the step count (1 to 32) and the caller as the approver, together with the chain's own block number and the time, and emits a Recorded event. The same wallet cannot record the same task and result twice; a new result for the same task is a new record.
Reads: entry(id), find(approver, taskHash, resultHash), idsByTask and idsByApprover (newest first, paged), recordCount(). Deployment takes about 640,541 gas and a first record about 218,000 gas. Address: not deployed yet. Until then, recording an approval is a practice signature kept in your browser, with no transaction and no gas.
A record proves that an address recorded these two fingerprints at that block. It does not prove the content is true, and it does not store any text.
Checking a task file
Download the task file of a completed task. It holds the task (brief, sources, template, permissions) and the result (research picks, draft, checklist, decision) as plain JSON, plus both hashes. Anyone can drop it on the ledger wall: the page rebuilds the canonical JSON, recomputes both hashes, tells you whether the file was changed after export, and lists the matching records on chain with approver, block and step count.
Live chain data
The site reads Robinhood Chain through its own read-only relay with public endpoints as fallback: the latest block and its pace, the gas price and the Chainlink ETH/USD feed. Once $AGENTLY launches, the token page also reads the token's name, symbol, supply, launchpad curve and holders. Numbers the site does not have are shown as a dash.
The $AGENTLY token
$AGENTLY is the token of the office on Pons, the Robinhood Chain launchpad. Planned uses are task credits, more workspace capacity and premium office features once hosted agents exist. None of these is live today; the office works fully without the token. See the token page.
Limits and privacy
- Tasks live in your browser. Clearing site data removes them, so keep task files you care about.
- Agents run in your browser tab; hosted agents that work while you are away are planned, not live.
- External tools such as web search, email or calendars are planned; today the agents read only what you paste and the chain readings.
- Drafts are drafts. A well-cited draft can still repeat a wrong source.
- The chat box at the bottom left talks only to the clerk in your own browser; nobody else sees it.
Questions
- What is Agently?
- Agently is a virtual agent office on Robinhood Chain. You assign a task with the sources to read; a researcher, a writer and a reviewer agent pass it desk to desk in a pixel office you can walk through, and you approve the result. An approved result can be recorded on chain as two fingerprints.
- How does Agently work?
- The researcher picks the source sentences that answer your brief, the writer fills a draft template from those picks with a source tag on every line, and the reviewer runs a fixed checklist. Sensitive tasks stop for your OK after research. Nothing is final until you approve it at the review desk.
- Do the agents make things up?
- The built-in methods cannot: the researcher only copies sentences from your sources and the writer only arranges them. When the site owner switches on the optional AI model, it is told to answer only from your sources, and the reviewer still flags lines whose words are not found in the cited source.
- Where are my tasks stored?
- In your own browser (local storage): tasks, sources, drafts, permissions and the timeline. They are sent nowhere unless an agent you allowed uses the AI model, which then receives the brief and the sources of that task only.
- What do tool permissions do?
- Each agent may only use the tools switched on at the elevator: reading pasted sources, reading Robinhood Chain, using the AI model, writing templates, running the checklist, exporting files. A step that needs a tool its agent does not have stops the task with the reason, and you can retry after changing the switches.
- What goes on chain?
- Only when you choose to record an approval: the keccak-256 hash of the task file, the hash of the result, the number of agent steps and your wallet address, in AgentlyTaskLedger. The contract is written and tested but not deployed yet, so recording is a practice signature for now. Texts never go on chain.
- Which network is Agently on?
- Robinhood Chain (chain id 4663), with ETH for gas. The wallet dialog adds the network to your wallet when you connect.
- How do I buy $AGENTLY?
- $AGENTLY has not launched yet. It will launch on Pons, and its contract address will be published on this site first. Ignore any address that does not come from here.
- What is $AGENTLY for?
- Planned uses are task credits, more workspace capacity and premium office features once hosted agents exist. None of that is live, and the office works fully without the token. It carries no promise of price, yield or reward.
- Do I need a wallet?
- No. Assigning, running and approving tasks all work without one. A wallet is needed only to sign an approval record.
- What are the risks?
- Drafts can still be wrong when the sources are wrong, so read them before you use them. Browser storage can be cleared, so download task files you want to keep. Tokens can lose all value. The ledger proves that an address recorded two hashes, not that the content is true.