Changelog

Until now you had to think in components: which agent does what, which schedule fires when, which trigger reacts to which event. Goals flips that around. Describe the outcome you want in plain text and Orqestr figures out the rest.

What's new

• Goal decomposition - type a goal like "Send me a daily Slack brief with revenue and churn" and the planner returns a full workflow: agents, integrations, schedules, triggers, and the knowledge each agent needs.
• One-click apply - review the proposed components, toggle anything you don't want, and create them all in a single transaction. Existing project resources are reused instead of duplicated.
• Persistent goal entity - once applied, the goal becomes a tracked entity with success criteria, progress notes, and a review cadence (hourly, daily, weekly, or custom cron).
• Autonomous review worker - a background worker checks each active goal on its cadence, evaluates progress against your success criteria, and spawns new tasks when needed. When the criteria are met, the goal is marked achieved.
• Goal context for agents - every task spawned from a goal carries the goal title, description, success criteria, and rolling progress notes into the agent's input. Agents stay aligned across runs without you re-explaining context.
• Plan-aware limits - maxConcurrentTasks and maxTasksPerReview cap how aggressive the worker can be, so a single goal can't flood your task board.

Where it lives

• Goals page - new "Goals" item in the project sidebar between Tasks and Activity. Type a goal at the top, see the plan preview, then create it. The list below shows all goals with status, plan setup progress, task counts, last reviewed time, and a "Review Now" button.
• Onboarding - new users now start by describing what they want their AI team to do. The same decomposition flow generates the starter agents, schedules, and triggers for the project.
• Landing page - try the planner without signing up at orqestr.ai. Type a goal, see the components Orqestr would build, then sign up to claim them. Free plan gets 1 active goal, paid plans get more.

Activity events

Goals are first-class in the Activity feed: goal.created, goal.plan_applied, goal.reviewed, goal.task_spawned, goal.achieved, plus pause/resume, archive, and resource link/unlink events. You can see exactly when the worker ran, what it decided, and which tasks it created.

Example workflows

• "Grow my X account to 5,000 followers" - planner sets up a content agent, an X integration, a daily research schedule, and a webhook trigger for replies.
• "Triage every new GitHub issue and post a daily summary to Slack" - planner wires up a triage agent, GitHub and Slack connections, an issues.opened trigger, and a daily summary schedule.
• "Send me a morning brief with revenue, signups, and churn" - planner creates a metrics agent, the relevant integrations, and a daily schedule.

Goals build on the knowledge system and event triggers shipped earlier this year. Together they're the foundation for letting agents own outcomes, not just tasks.

The X integration is no longer just inbound. Your agents can now take action on X directly.

What's new

• 14 agent tools for X - post tweets, reply, quote, delete, search recent tweets, like/unlike, retweet/unretweet, send DMs, follow/unfollow, look up users, and fetch user timelines.
• OAuth 1.0a user-context auth - agents act as your X account using your own API credentials. All API calls are signed per-request.
• Webhook is now optional - the Bearer Token field is no longer required. Connect with just your OAuth 1.0a credentials to give agents tools without setting up webhooks. Add the Bearer Token later if you want inbound event triggers too.
• Per-agent capability control - assign X tools to specific agents and set per-tool permissions (allow, require approval, or disable).

Available tools

Example workflows

• A growth agent that monitors mentions via webhook triggers, then replies and follows back automatically
• A content agent that researches trending topics with search_tweets, drafts a thread, and posts it
• A support agent that watches for DM events and responds with send_dm

Building on the webhook integration from last week, you now have a complete two-way X integration: listen to events and act on them, all from the same connection.

You can now connect X (Twitter) as an event source and trigger agent workflows from real-time events.

What's new

• X webhook integration in the integrations catalog. Provide your X app credentials (Bearer Token + Consumer Secret) and Orqestr registers a per-connection webhook automatically.
• Event triggers for X — create triggers for tweet events, follows, DMs, favorites, and more. Use filters to narrow which events create tasks.
• Per-connection CRC validation — each connection handles X's challenge-response checks independently using its own credentials.

How it works

1. Add the X integration from the Integrations page
2. Enter your X app credentials (OAuth 1.0a keys for agent tools, plus Bearer Token for webhooks)
3. Create an Event Trigger under Tasks > Triggers and select your X connection
4. Pick the events you care about (tweets, follows, DMs) or enter a custom event type
5. Matching events automatically create tasks and route them to the right agent