A tool built around the way a team works

Recurring tasks and record structure

A first view can focus on a recurring job such as checking inventory, looking up a lead or marking a support request. The brief names the records and the action needed with them. This scope provides the coding agent with a specific task and gives the team a result to check against real data before the tool expands into a larger workflow.

A kanban card records the fields, intended users and whether the tool reads from an existing file or starts empty. A sample of actual data can be attached as a workspace file. That sample supplies the structure for the build instead of leaving the agent to guess the shape of the records.

Scoped views built from sample data

Assign to agent can send the card to a coding agent, or the task can be described to Claude Code, Codex CLI, opencode, Cursor CLI or Qwen Code, with Antigravity available from the terminal. The task specifies fields, an action and a list or table view. Filtering, editing or a second view can become separate cards after the initial result is reviewed.

The codespace runs Linux. Agent sign-ins or API keys are supplied separately, and tools such as a database or spreadsheet library can be installed for the build. VS Code provides access to inspect the logic and compare it with the intended action.

Public URLs and explicit access controls

Every codespace has a public URL. The Public site panel points it at the tool’s port for review with real or sample data. Anyone with the link can reach a public URL. Oyren does not add a login to the tool automatically. Restricted use requires an implemented login step and care over where the link is shared.

Runtime is billed by the hour while the codespace runs. A snapshot supports pausing the machine and returning to the data and build later. The board and supporting notes keep the original scope available for the next view or change, alongside the action and access requirements already recorded.

Questions about a tool built around the way a team works

Is the tool private to my team by default?

No. Anyone with the codespace’s public URL can reach it. Oyren does not add a login automatically. Restricted access requires authentication implemented by the coding agent, with the link kept out of public locations.

Can the tool read data I already have, like a spreadsheet?

Yes. A file can be attached to the board card or workspace so the agent builds from its data structure. Records in the result need comparison with the source before the tool is relied on.

How small can a first version be?

An initial scope can be a list and an action, such as adding a row or marking a status. Further views or actions can be separate board cards after the first result is checked against the brief.