Agent Missions MVP: settings, missions API, tracker actions, Telegram /mission#2
Draft
computerbox124 wants to merge 2 commits intodevelopfrom
Draft
Agent Missions MVP: settings, missions API, tracker actions, Telegram /mission#2computerbox124 wants to merge 2 commits intodevelopfrom
computerbox124 wants to merge 2 commits intodevelopfrom
Conversation
- Extend ai-bot REST DTOs and pod-ai-bot: agent profiles, executors, missions CRUD - Allowlisted executor spawn (default cat; MISSION_CODEX_COMMAND / MISSION_CURSOR_COMMAND) - Mission context from tracker (classic bucket=todo|backlog), cap 20 tasks - Post results as issue comments; resolve agent by id/name/role - Settings Agent Missions + Run Agent Mission popup from tracker actions - Telegram: /mission parser, AI_BOT_URL to pod POST /missions, multi-workspace hint - Tests: output normalization, mission command parsing Co-authored-by: Huseyn Hajiyev <computerbox124@users.noreply.github.com>
…d env filter - Extract resolveMissionExecutor for pure unit tests - Cover explicit/default/shared fallback, private access, busy shared - Add filterExecutorEnv tests with mocked config - Expand Telegram missionParse tests (workspace, task, invalid scope) - gitignore qa-artifacts for local recordings Co-authored-by: Huseyn Hajiyev <computerbox124@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the Agent Missions MVP as a thin extension on existing pod-ai-bot (Mongo config DB), ai-bot REST types, ai-bot-resources UI, model-ai-bot settings category, tracker actions, and pod-telegram-bot
/missioncommand.Backend (pod-ai-bot)
agentProfiles,executorResources,missions/agent-profiles,/executor-resources,/missions,/mission-channels/status(Bearer workspace token)executorTypeon create when no default)MISSION_CODEX_COMMAND/MISSION_CURSOR_COMMAND(defaults tocatfor demo), stdin prompt, timeout, output capagent=CTO)Client
Telegram (pod-telegram-bot)
/missionwithmissionParse.ts+mission.tscallingPOST {AI_BOT_URL}/missionsworkspace=when multiple integrations existAutomated QA (unit tests)
src/missions: output normalization, executor resolution (explicit, default, shared fallback, private access, busy shared), filterExecutorEnv (mocked config)missionParse: basic parse,workspace=,task=+ scope=task, invalid scopeManual / E2E
Full Huly stack (accounts, transactor, Mongo, browser login) required for UI E2E; not run in CI agent VM.
Tradeoffs / deferred
catunless env overrides to real CLI tools