Pragmos Beta 1 is receiving a focused update as we move toward Pragmos Beta 2. This release prioritizes a more stable and cohesive core experience while eliminating several unwanted bugs.

A core pillar of Pragmos is groups. Groups serve as centralized spaces where people can work linearly together - scheduling events, completing projects, tracking progress, and delegating tasks efficiently.

In future releases, we plan to deepen this capability by letting users explicitly define their knowledge domains, specialties, and preferences. This will help agents understand you more accurately and deliver better, more personalized results.

Bug Fixes

This update addresses several issues that, while not core-breaking, were tedious or frustrating. Here’s what we fixed:

• Infinite Agent Loops: In some cases, dispatching an agent would trigger a confirmation request that could loop indefinitely. This has been resolved. Agents operate with a high degree of autonomy (minimal human intervention), so if you encounter any unexpected behavior, please reach out to us.
• Double Replies: Replies to communications sometimes appeared twice until the web app was reloaded. Responses now populate only once.
• Logging Out: A backend issue prevented reliable logouts. This has been fixed - you can now sign out cleanly.
• Adding TODOs: The “Add TODO” button on the main dashboard was broken in the initial Beta 1 release. It now works as expected.

We’ve also made a range of quality-of-life improvements across both the backend and frontend to create a smoother overall experience.

A More Adhesive Core

Every part of Pragmos should connect meaningfully with the rest. In the original Beta 1 release, adding projects, TODOs, or events to a group only updated the schedule inside that group.

This update adds proper population of members’ individual schedules. When you add an event, TODO, or project to a group and assign one or more people, the item appears only on their schedules and dashboards. If no individual assignees are specified, it populates every member’s schedule and dashboard.

Looking ahead, we will further strengthen this adhesion by tracking the origin of scheduled items, TODOs, and projects. You’ll be able to see when something comes from a group and who else has been assigned to it.

Subsequent updates will continue to emphasize adhesive centralization and practical feasibility - ensuring the different parts of Pragmos relate to one another elegantly, making the product easier to navigate and more powerful to use.

Agents Understand Availability Better

In the original Pragmos Beta 1 release, agents had only minimal insight into your availability. This update gives them a complete view of your availability and what it represents. As a result, agents can make more informed decisions about when you’re free and how that availability intersects with your current schedule - leading to better and more accurate agent-to-agent communication.

Agents now also take incoming and outgoing schedule requests into account. Because a pending request sits in a gray area (it may or may not ultimately be added), agents treat the proposed times as reserved. This helps protect those requests and reduces the chance of scheduling conflicts or errors.

Up Next On Our Agenda

Following this release, we will begin focusing on the following:

• Dedicated Projects Page: A new centralized space built around a single project, its progress, and its TODOs. Assignees will be able to contribute, communicate, track progress, post updates, file issue reports, and further delegate tasks to more specialized individuals.
• Configurable Agent Denials: Currently, agents are only tasked with finding a mutually available time. They do not yet conclude that two schedules are fully incompatible. We will give agents the ability to end a conversation when no suitable overlap exists and deliver a customizable message you’ve configured in your account - whether that’s contact information, an apology, or any other note you’d like to leave.
• Agent Communications: Closely related to the above, agents will be able to leave descriptive messages for you. For example, if an agent determines there is no schedule compatibility and you have agentic communications enabled, it will leave a clear note explaining the situation and relevant details.
• More Descriptive TODOs: TODOs already support due dates inside groups, but the main dashboard currently lacks this. We will add due-date support across the product. In addition, TODOs will be able to be linked to a specific project so the association is visible both on the dashboard and within the project itself.
• Expanded Voice Assistance: Pragmos is built around the ability to speak and have the system act. We are extending voice support into agent dispatching and group scheduling. You’ll be able to describe your intent, and Pragmos will draft the appropriate agent dispatch. This also lays the foundation for a more unified group experience, as the system will be able to factor in everyone’s availability when proposing new items - reducing conflicts and increasing compatibility.
• More Standard Accounts: Currently, the only forward-facing details of other group members are their name, profile picture, and schedule. We will introduce a proper account view that consolidates a user’s profile picture, username, schedule, and availability into a single place. The existing page for viewing a user’s schedule and sending scheduling requests will be retired, as the new account experience will replace and improve upon it.