osFoundry / Platform
Issues
Lightweight issue tracking — labels, assignees, comments. Agents can file and close them.
What it is
Issues is osFoundry's built-in issue tracker for the Code & Build workflow. It keeps the parts of issue tracking you actually use — a title, a description, labels, an assignee, and a comment thread — and leaves out the ceremony. Because it lives inside the same desktop workspace as your chat, agents, code, and knowledge, an issue is never a browser tab you switch away to; it sits next to the work it describes.
What makes it different is that your AI agents are first-class participants, not spectators. An agent working through a task can file a new issue when it hits something worth tracking, drop a comment with what it found, and close the issue once the work is done — the same actions a person takes, driven by the agent as it runs. You review the thread and the labels the same way you would for a teammate. Everything runs under osFoundry's bring-your-own-key model, so the models doing that work call your own API keys with no reseller markup, and the local-first design means your issue data can stay on your device rather than living on someone else's tracker.
It matters because most issue trackers are built for large teams and heavy process. If you are one person or a small group building software with AI agents in the loop, you want somewhere to write down what needs doing, tag it, assign it, and talk about it — without per-seat fees or a separate service to log into. Issues gives you that lightweight surface and connects it directly to the agents already doing the building.
Key capabilities
- File issues with a title, description, labels, and an assignee — no required fields or workflow states to configure first
- AI agents can open, comment on, and close issues as they work, so tracking stays current without manual bookkeeping
- Organize with free-form labels and route work by assigning issues to a person or an agent
- Discuss in threaded comments attached to each issue, keeping context in one place instead of scattered across chats
- Lives in the same desktop workspace as your code, chat, and agents, and runs on your own API keys with no per-seat fees
Use cases
- Solo developer: files quick issues for bugs and TODOs while building, then lets an agent pick them up, comment progress, and close them
- Small engineering team: tags work with labels and assigns issues to teammates or agents without paying per-seat tracker fees
- Agent-driven workflow: an automated agent discovers a problem mid-run, opens an issue with the details, and resolves it once fixed
Frequently asked questions
Can AI agents actually create and close issues, or just read them?
They can do both. An agent running in osFoundry can file a new issue, add comments, and close it when the work is finished — the same file-and-close actions a person performs, so tracking stays up to date as the agent works.
How is this different from GitHub Issues or Jira?
It is deliberately lightweight — labels, assignees, and comments, with no boards, sprints, or required workflow states to set up. It runs inside your osFoundry desktop workspace next to your code and agents, with no per-seat fees, and your data can stay local rather than on a hosted service.
Do I need a subscription or paid seats to use Issues?
No per-seat fees. Issues is part of the osFoundry workspace, and any AI work involved runs on your own API keys under the bring-your-own-key model, so you pay your model provider directly with no reseller markup.