Skip to main content

Using the demo

Every new ACE Dev account comes with a ready-made project called Trakk, a lightweight issue tracker in the spirit of Jira. It is a playground: a real, working application you can ship features into without connecting any of your own code.

No setup required

Trakk arrives already mapped. Its repository is connected and its codebase is fully discovered, so you can skip Create a project, Connect a repository, and Map your codebase, and go straight to asking for a feature.

What Trakk is​

Trakk is a small issue tracker with projects, tickets, and a Kanban board. Because ACE Dev has already mapped it, the agents know where the code lives and how it fits together. That makes the demo the fastest way to see the whole Software Factory flow, from a plain-language request to a feature you can run and check.

Signing in to Trakk​

Trakk only runs inside ACE Dev. You open it through a local environment while you review your work, and you never merge it or deploy it. You do not need to connect a GitHub account to use it. The login screen expects these shared demo credentials:

FieldValue
Emailadmin@trakk.local
Passwordadmin123
Demo only

These credentials exist for the shared Trakk demo. They are not tied to your ACE Dev account, and they do not apply to any project of your own.

The example: an Archives tab​

In this walkthrough you ask ACE Dev for a new Archives tab, with two areas: an archive for projects and an archive for tickets. Archiving reuses Trakk's existing soft delete, while permanently deleting an item invokes the hard delete. From the tab you can restore an item or permanently delete it, sort newest first with the option to reverse the order, and filter by project, label, who archived the item, and priority.

Step 1: Create a card​

Open Software Factory → Development to see the Kanban board. Create a new issue card, name it Archive tab, and paste your request:

Add an Archives tab below Projects. In this Archives tab I want two areas,
the projects archive and the tickets archive.

Both projects and tickets already have hard and soft delete. Soft delete is
the one that should be used for archiving; permanently deleting an item,
through its own UI or the Archives tab, should invoke the hard delete.

- Both should have the option to restore or permanently delete an item.
- Default display order should be newest to oldest, with the option to reverse it.
- Filter modes are: per project, per label, per user who archived the item,
and per priority tag.

Create the issue. The card lands in the Backlog.

Step 2: Start the flow​

Drag the card from Backlog to In Progress. This kicks off the whole chain of events: ACE Dev triages the request and dispatches a planning sub-agent.

Open the card to follow along. The Comments tab narrates progress in plain language, and here it reports that planning has been dispatched.

For a closer look, open Technical details. This is the execution-level view, a terminal-style trace of what each agent and sub-agent is reasoning about, turn by turn. The planning sub-agent keeps iterating until it has a plan ready for you.

Step 3: Review and approve the plan​

When planning finishes, the card moves to In review and a plan appears, with the ordered sub-cards ACE Dev intends to build and any open questions for you. Read it, then approve, request changes, or reject.

Approval required

Nothing is written to Trakk's files before you approve the plan.

Step 4: Follow the tasks​

Once you approve, ACE Dev dispatches the work as sub-tasks and the master card returns to Running. To watch the individual pieces, switch the board filter from Stories to Tasks: each sub-card appears in To Do in its planned order of execution, then moves to In Progress one at a time.

The master card is your source of truth. It stays updated with progress, tracks each sub-task from To Do to Done, and surfaces any question an agent has for you.

Keep the board clean

Leave the filter on Stories for a less cluttered board, and do most of your work from the master card.

Inside Technical details → Execution trace, the Orchestrator is the main agent. Under it you can watch each sub-agent run, such as the implementation sub-agent writing the code.

Step 5: Review with a local environment​

When the work is done, the master card returns for a final approval gate. Before you decide, open a local environment to inspect and test the result yourself. It gives you the exact files ACE Dev touched, so you can review them, change things by hand, and run the app to check your feature.

Open a local environment from the card, or from Software Factory → Local environment in the sidebar. Each card the agent has worked on has its own workspace, with a status such as Ready or Asleep. When it is ready, click Open in VS Code.

Once VS Code opens, run the execution script in its terminal. In the example below, the script is ./sandbox-setup.sh. It starts the app, so you can see your feature live.

Open the running app. Trakk's login screen appears. Sign in with the demo credentials above (admin@trakk.local / admin123), then check your feature.

Step 6: Confirm the card, or request changes​

Back on the card, the final approval gate gives you three choices: Accept, Request changes, or Reject.

If the feature works the way you want, confirm the card. What happens next depends on the project:

  • A real app on your repository: confirming opens a pull request, which you review and merge in ACE Dev.
  • The Trakk demo: there is no pull request. The card simply moves to Done on the board.

If something is not right, request changes on the card, and describe what to fix. The agents update the implementation and the card returns to the same gate. Open the local environment again and check the result. Repeat as many times as you need. Only confirm the card after you have checked the app again and it works the way you want. That is the right workflow.

That is a complete feature, from a one-paragraph request to a working app you tested yourself, with your approval at every gate.

Next steps​

  • Ready to work on your own code? Follow Ship your first feature on a repository you connect yourself.
  • Try Talk to ACE Dev to run this same flow from the Chat tab, in plain language.
  • Explore Core Concepts to understand the Software Factory, agents, and workflows in more depth.