Agent

Hands on the machine.

Onyra is not a chat window with opinions. It is being built to touch files, run commands, remember on disk, and stop itself when a step crosses a line you drew.

Pre-release These are the capabilities as designed. You cannot install the agent today. The roadmap is the order they are planned to arrive.

01

Files and commands

The work lives in a directory. Onyra edits the files and runs the commands the task actually needs. You can open that directory and read what changed. Nothing important is trapped in a scroll of messages.

Exampleedit  notes/brief.md
run   ls -la ./site

02

A browser

Some tasks are not finished until someone looks at the page. The agent can open a browser to read documentation, check a result, or confirm the link it just published. The browser is a tool, not a place the work disappears into.

Exampleopen  the page it just hosted
read  the title, the layout, the broken link

03

Memory on disk

Plans, notes, and preferences are written down as files. A later task can pick them up. You can move them, edit them, or delete them. Memory you cannot open is not memory you control.

Examplememory/
  brief.md
  plan.md
  preferences.md

04

Auto mode, with a judge

Auto mode is allowed to continue without asking on every small step. Before it spends, deletes, or publishes, a safety judge reads the plan and can refuse it. The judge is a gate, not a promise that nothing can go wrong. You still set the rules, and you can still read the result.

Examplejudge  spend under ceiling
judge  no secrets in the page
hold   if either fails

05

Delegation

A large brief can be split. Onyra can hand a slice to a helper agent and gather what comes back. You still see one brief and one result. Helpers do not get a quieter set of rules than the agent you spoke to.

Exampledelegate  research the sources
delegate  draft the page
return    one link, one report

06

Chat apps

The desk does not have to live in one window. Telegram, Discord, and Slack are planned as doors to the same agent: you send a brief from the place you already are, and the work still lands in files, a link, and a receipt.

Planned doorsTelegram
Discord
Slack

07

MCP, plugins, skills

The agent is meant to grow by connection, not by becoming a closed box. MCP servers, plugins, and skills are how a new tool joins the desk. What it is allowed to spend and publish still passes through the same ceiling and the same judge.

Exampleconnect  an MCP server
load     a skill
limit    unchanged

The machine is only half the desk.

Work on your computer pauses when the computer does. The cloud is the room that stays open, and the wallet is how the calls get paid. Neither is live yet. Both are written down so the build can be held to them.